Kernel-level use-after-free allowing potential kernel RCE in the Linux HID subsystem; Linux kernel is ubiquitous and a kernel RCE can disrupt organizations.
CVE-2026-90329
Linux HID race causes kernel use-after-free enabling kernel-level RCE via malicious HID reports
do firstUpgrade to a fixed release: < 3.10, >= 5.10.270 and <= 5.10.*, >= 5.15.221 and <= 5.15.*, >= 6.1.188 and <= 6.1.* (+5 more below).
Is CVE-2026-90329 being exploited?
Not confirmed. CVE-2026-90329 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.34% probability of exploitation in the next 30 days.
How severe is CVE-2026-90329?
CVE-2026-90329 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-90329?
Yes. A fix has been recorded for CVE-2026-90329. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-90329 affect?
CVE-2026-90329 affects Linux kernel (HID subsystem), systems using hidraw/hid drivers, hosts accepting USB/Bluetooth HID devices. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-90329?
Install vendor kernel updates with the HID fixes and block untrusted HID devices
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Concurrent HID report callbacks can trigger a use-after-free, allowing a local/physical attacker with a malicious HID (USB/Bluetooth) to achieve kernel RCE or privilege escalation.
Immediate action required
- affected>= c849a6143bec520aff2a6646518b0d041402428b and < 3ffb088a2ed34ca982cfc2c81d107ce370aa45f1
- affected>= c849a6143bec520aff2a6646518b0d041402428b and < 2c35cdeb13a0c52429501e66f368fa59cad235f6
- affected>= c849a6143bec520aff2a6646518b0d041402428b and < 98201b46f7e33fe11af6f024fecb40fb56634225
- affected>= c849a6143bec520aff2a6646518b0d041402428b and < 9a3da56aae28e1ad3a3e591f72a537742053ecd2
- affected>= c849a6143bec520aff2a6646518b0d041402428b and < edd490b8ad85c052eaf10dcc9f390ea54f1e1b39
- affected>= c849a6143bec520aff2a6646518b0d041402428b and < 01eeb601a1626e683fb7b77c63f442b06fb87093
- affected>= c849a6143bec520aff2a6646518b0d041402428b and < b85d1000eb8842768970f2fd0a8fd362472d02d5
- affected>= c849a6143bec520aff2a6646518b0d041402428b and < 207853d46f7ef2e28042344a1468da8754c3ddbf
- affected3.10
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
timeline
- 17 Sept 2026Published
- 19 Sept 2026Analysed by vulneraibility.com · 2 days later
- 19 Oct 2026CVE record last updated · 30 days later
- Linkgit.kernel.org /stable/c/3ffb088a2ed34ca982cfc2c81d107ce370aa45f1
- Linkgit.kernel.org /stable/c/2c35cdeb13a0c52429501e66f368fa59cad235f6
- Linkgit.kernel.org /stable/c/98201b46f7e33fe11af6f024fecb40fb56634225
- Linkgit.kernel.org /stable/c/9a3da56aae28e1ad3a3e591f72a537742053ecd2
- Linkgit.kernel.org /stable/c/edd490b8ad85c052eaf10dcc9f390ea54f1e1b39
- Linkgit.kernel.org /stable/c/01eeb601a1626e683fb7b77c63f442b06fb87093
- Linkgit.kernel.org /stable/c/b85d1000eb8842768970f2fd0a8fd362472d02d5
- Linkgit.kernel.org /stable/c/207853d46f7ef2e28042344a1468da8754c3ddbf
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.