Multiple Linux kernel HID and force-feedback drivers contained out-of-bounds write vulnerabilities tracked as CVE-2019-19532. A malicious USB HID device could trigger the flaws on kernels earlier than 5.3.9, affecting drivers for force-feedback hardware from vendors including Logitech, Microsoft, Sony, and Holtek.
The upstream fix in commit d9d4b1e46d95 validates that a HID device has input entries before drivers access the first hid_input structure. Drivers now log “no inputs found” and return -ENODEV for malformed devices, preventing invalid list access that could cause kernel crashes or denial of service. Organizations using affected Linux kernels should deploy kernel 5.3.9 or applicable vendor security updates from Ubuntu, Debian, or openSUSE.

See affected versions and whether adversaries are exploiting it.
4 events from the most recent confirmed update back to the earliest known activity.
The CVE-2019-19532 record was updated by MITRE, its CNA.
CVE-2019-19532 was published for multiple out-of-bounds write vulnerabilities in Linux kernel HID drivers affecting versions before 5.3.9. A malicious USB device can trigger the flaws; the issue is also identified as CID-d9d4b1e46d95.
Ubuntu issued USN-4226-1, Debian issued DLA 2068-1 and DLA 2114-1, and openSUSE issued openSUSE-SU-2020:0336 for Linux security updates related to the HID-driver vulnerability.
A Linux kernel change added empty-list checks to multiple HID force-feedback driver initialization routines, causing them to log an error and return -ENODEV when a device has no registered input entries. The change prevents invalid HID input-list dereferences that could crash the kernel.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
See whether adversaries are exploiting this yet, and where the affected versions run in your environment.
3 references tracked. Mallory keeps watching after this page renders.
cve.mitre.org
Open sourcegit.kernel.org
Open sourcepatchwork.kernel.org
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.