CVE-2026-90329: HID: synchronize input before cleaning up a failed probe
Noroxi assessment
Priority: Monitor (action score 35/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.34% (FIRST EPSS).
- Someone on the same network segment can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 01eeb601a1626e683fb7b77c63f442b06fb87093, 207853d46f7ef2e28042344a1468da8754c3ddbf, 2c35cdeb13a0c52429501e66f368fa59cad235f6; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1.
Low priority for now. Upgrade to Linux Linux 01eeb601a1626e683fb7b77c63f442b06fb87093, 207853d46f7ef2e28042344a1468da8754c3ddbf, 2c35cdeb13a0c52429501e66f368fa59cad235f6; azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 6.6.157.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: HID: synchronize input before cleaning up a failed probe hid_device_io_start() allows reports to run concurrently with probe. If the probe subsequently fails, __hid_device_probe() releases driver resources and clears hdev->driver without first excluding those report callbacks. For example, a report may enter hidraw_report_event() while the failure path frees the associated hidraw object, leading to a use-after-free when the report takes the object's list lock. Stop input before performing failed-probe cleanup. This reacquires driver_input_lock and waits for any report callback already in progress.
- Published
- Sep 17, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.3% · 28th percentile
- CWE
- —
Report tools
Action score
35
Monitor
Low priority for now.
- CVSS
- 35 / 40 · 8.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CNA vs NVD score
- NVD
- —
- CNA · Linux
- 8.8
- NVD has not scored this yet; the score shown is the CNA’s.
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 3.10affected
- c849a6143bec520aff2a6646518b0d041402428b and later · before 3ffb088a2ed34ca982cfc2c81d107ce370aa45f1affected · git
- c849a6143bec520aff2a6646518b0d041402428b and later · before 2c35cdeb13a0c52429501e66f368fa59cad235f6affected · git
- c849a6143bec520aff2a6646518b0d041402428b and later · before 98201b46f7e33fe11af6f024fecb40fb56634225affected · git
- c849a6143bec520aff2a6646518b0d041402428b and later · before 9a3da56aae28e1ad3a3e591f72a537742053ecd2affected · git
- c849a6143bec520aff2a6646518b0d041402428b and later · before edd490b8ad85c052eaf10dcc9f390ea54f1e1b39affected · git
- c849a6143bec520aff2a6646518b0d041402428b and later · before 01eeb601a1626e683fb7b77c63f442b06fb87093affected · git
- c849a6143bec520aff2a6646518b0d041402428b and later · before b85d1000eb8842768970f2fd0a8fd362472d02d5affected · git
- c849a6143bec520aff2a6646518b0d041402428b and later · before 207853d46f7ef2e28042344a1468da8754c3ddbfaffected · git
- before 3.10not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.190-1 | 6.1.190-1 |
| Debian:12 | linux-6.12 | before 6.12.111-1~deb12u1 | 6.12.111-1~deb12u1 |
| Debian:13 | linux | before 6.12.111-1 | 6.12.111-1 |
| Debian:14 | linux | before 7.2.6-1 | 7.2.6-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-90327Sep 17, 2026 · phonet: pep: do not write beyond optlen in getsockopt0Monitor
- ← EarlierCVE-2026-90328Sep 17, 2026 · HID: steam: Reject short reads0Monitor
- Later →CVE-2026-90330Sep 17, 2026 · HID: logitech-hidpp: Fix FF device cleanup on init failure0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01eeb601a1626e683fb7b77c63f442b06fb87093 | Vendor (CNA) |
| Linux Linux | 207853d46f7ef2e28042344a1468da8754c3ddbf | Vendor (CNA) |
| Linux Linux | 2c35cdeb13a0c52429501e66f368fa59cad235f6 | Vendor (CNA) |
| Linux Linux | 3ffb088a2ed34ca982cfc2c81d107ce370aa45f1 | Vendor (CNA) |
| Linux Linux | 98201b46f7e33fe11af6f024fecb40fb56634225 | Vendor (CNA) |
| Linux Linux | 9a3da56aae28e1ad3a3e591f72a537742053ecd2 | Vendor (CNA) |
| Linux Linux | b85d1000eb8842768970f2fd0a8fd362472d02d5 | Vendor (CNA) |
| Linux Linux | edd490b8ad85c052eaf10dcc9f390ea54f1e1b39 | Vendor (CNA) |
| azl3 kernel 6.6.150.1-1 on Azure Linux 3.0 | — | Microsoft (MSRC) |
| azl3 kernel 6.6.152.1-1 on Azure Linux 3.0 | 6.6.157.1-1 · Release Notes | Microsoft (MSRC) |
| debian:linux | 6.1.190-1 · Debian:12 | Package registry (OSV) |
| debian:linux | 6.12.111-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.111-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone on the same network segment can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Adjacent
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/207853d46f7ef2e28042344a1468da8754c3ddbf
- git.kernel.org/stable/c/2c35cdeb13a0c52429501e66f368fa59cad235f6
- git.kernel.org/stable/c/3ffb088a2ed34ca982cfc2c81d107ce370aa45f1
- git.kernel.org/stable/c/98201b46f7e33fe11af6f024fecb40fb56634225
- git.kernel.org/stable/c/9a3da56aae28e1ad3a3e591f72a537742053ecd2
- git.kernel.org/stable/c/b85d1000eb8842768970f2fd0a8fd362472d02d5
- git.kernel.org/stable/c/edd490b8ad85c052eaf10dcc9f390ea54f1e1b39
Vendor advisories and official records. Exploit/PoC links are deliberately left out.