Kernel crash via fieldless HID report
Published May 6, 2026 · Updated May 6, 2026
NULL pointer dereference in the Linux Kernel HID++ driver allows physically proximate attackers to crash the kernel through a USB device. hidpp_get_report_length() indexes report->field[0] when a crafted HID output report exists but maxfield is zero, leaving no valid field to dereference. Exploitation requires attaching a fake USB gadget that supplies its own malicious HID report descriptor, and the reported consequence is a kernel crash.
Summary
What happened
NULL pointer dereference in the Linux Kernel HID++ driver allows physically proximate attackers to crash the kernel through a USB device. hidpp_get_report_length() indexes report->field[0] when a crafted HID output report exists but maxfield is zero, leaving no valid field to dereference. Exploitation requires attaching a fake USB gadget that supplies its own malicious HID report descriptor, and the reported consequence is a kernel crash.
The record
- CVE
- CVE-2026-43136
- Published
- May 6, 2026
- Updated
- May 6, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1499
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 6, 2026CVE publishedPublication date reported by the CVE source.
- May 6, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1547d41f9f19d691c2c9ce4c29f746297baef9e9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <1acb28123e57b50d737377f400f57eec889fe5e4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <2dc023dbc11b8dfa8afa63242762acd8cddcad03
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7f59999fcd699af06ad2aef446a635ea6aa87db3
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ae81fac9ce81917817d787e6b74e68482d99bdf2
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <b74bf7d0d01fa9b53653f58c29aa00772121f6e9
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <f1ceaaf93ea32d0f2b95c95f784ee155962c52ad
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <fb1725c0804dbec9dd01c4cb5c9f1f77a69e36dc
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo