CVE-2026-80780
Received Received - Intake

Out-of-Bounds Write in Linux Kernel HID Force Feedback

Vulnerability report for CVE-2026-80780, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-09-04

Last updated on: 2026-09-04

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: HID: pidff: fix OOB write when hid->inputs is empty hid_pidff_init_with_quirks() derives its input_dev from list_entry(hid->inputs.next, struct hid_input, list) without first checking that hid->inputs is non-empty. The list member of struct hid_input is at offset 0, so on an empty list list_entry() yields &hid->inputs itself and the following hidinput->input load reads an unrelated member of struct hid_device. dev is then a type-confused pointer, and force-feedback init writes through it: each set_bit(FF_*, dev->ffbit) stores 8 bytes at dev + 192, past the end of the object dev actually aliases, and input_ff_create() adds further writes of a heap pointer and two function pointers. Until hid-universal-pidff the only caller was hid_pidff_init() from usbhid, which runs under HID_CLAIMED_INPUT and therefore always has at least one hid_input. universal_pidff_probe() starts the device with HID_CONNECT_DEFAULT & ~HID_CONNECT_FF and then calls hid_pidff_init_with_quirks() directly whenever the descriptor carries a PID usage page, bypassing that gate. A report descriptor whose only application collection is on HID_UP_PID leaves hid->inputs empty while hid_connect() still succeeds through the hidraw claim, so probe reaches the unguarded list_entry(). The write happens in the USB probe path, on the hotplug workqueue, so plugging in a malicious device is enough to trigger it; no attacker software and no logged-in user are required. KASAN reports an 8-byte out-of-bounds write in hid_pidff_init_with_quirks() reached from universal_pidff_probe(). Check for an empty list before deriving dev and return -ENODEV, as the other HID force-feedback drivers already do. universal_pidff_probe() propagates the error and unwinds. Discovered by XBOW, triaged by Baul Lee <baul.lee@xbow.com>

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-04
Last Modified
2026-09-04
Generated
2026-09-04
AI Q&A
2026-09-04
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
linux linux_kernel *

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is an out-of-bounds (OOB) write in the Linux kernel's HID force-feedback (pidff) driver. It occurs when the hid->inputs list is empty, causing list_entry() to return an invalid pointer. This leads to type confusion where the driver writes past the end of a heap object, including function pointers, during USB device probe.

Detection Guidance

This vulnerability is specific to the Linux kernel's HID force-feedback subsystem and requires kernel-level detection. Check if your kernel version includes the vulnerable code path by examining the hid-pidff driver. Use commands like 'modinfo hid-pidff' or 'dmesg | grep pidff' to inspect driver status. A KASAN report indicating an 8-byte out-of-bounds write in hid_pidff_init_with_quirks() would confirm exploitation.

Impact Analysis

An attacker can exploit this by plugging in a malicious USB device to trigger the OOB write. This could crash the system, corrupt memory, or potentially execute arbitrary code with kernel privileges. No user interaction or software installation is required.

Compliance Impact

This vulnerability involves an out-of-bounds write in the Linux kernel's HID force-feedback subsystem, triggered by a malicious USB device. It does not directly impact data privacy or security controls required by GDPR or HIPAA. However, if exploited, it could lead to system instability or crashes, potentially disrupting compliance with availability requirements in these regulations.

Mitigation Strategies

Update your Linux kernel to a patched version where the fix is applied. The patch adds a check for an empty list before deriving the device pointer. If immediate patching is not possible, avoid using HID devices with PID usage pages until the kernel is updated.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-80780. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart