HID: wacom: stop hardware after post-start probe failures
In the Linux kernel, the following vulnerability has been resolved: HID: wacom: stop hardware after post-start probe failures wacom_parse_and_register() starts HID hardware before registering inputs and initializing pad LEDs/remotes. Those later steps can fail, but their error paths currently release Wacom resources without stopping the HID hardware. Route post-hid_hw_start() failures through hid_hw_stop() before releasing driver resources. This issue was identified during our ongoing static-analysis research while reviewing kernel code.
- Published
- Aug 10, 2026
- Updated
- Aug 17, 2026
- EPSS
- 0.4% · 33th percentile
- CWE
- —
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
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.4%
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.
Affected systems
—
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
- d943536197c1a05e377452af4ec7942e11d018f4, dbaca8fa9ec2c5aa55ec515686ce3b9007554eab, 79187e8099a9feb550916dbfb962497522022b6d, 6.8affected
- f304eb483393f135ab479d02da6f5dc7d9b51cd6 and later · before 5a7ca028facf04921b2c1c2e4d1ee7f282510555affected · git
- 853307924a9003b3142b5253b1caa6625fbad9fc and later · before 3e6473a4f0596182acdda5219b4bebfbee76514faffected · git
- e5c6c8ef3e4d3a88407404daafbf2c6be62f2185 and later · before 46d8b8c85ae0589fb85746a64e8908160e52aac3affected · git
- fc41101a94b11cd0d5ad8e213b2b6965f248d653 and later · before 1a1ebdcb56ae58a0ee2c54dd15d75121e30424e3affected · git
- c1d6708bf0d3dd976460d435373cf5abf21ce258 and later · before 75eb2173b63ab41c24d80cd641af18f3c117a267affected · git
- c1d6708bf0d3dd976460d435373cf5abf21ce258 and later · before 416095e9a6037b4b39fcadd0d2bd77a8852211ecaffected · git
- c1d6708bf0d3dd976460d435373cf5abf21ce258 and later · before e2cc711a9df37f359159b21db56cea9c21f58a9caffected · git
- c1d6708bf0d3dd976460d435373cf5abf21ce258 and later · before ec2612b8ad9e642596db011dd8b6568ef1edeaa1affected · git
- 5.10.210 and later · before 5.10.261affected · 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.180-1 | 6.1.180-1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-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
- CVE-2026-74309vdpa/octeon_ep: fix IRQ-to-ring mapping in interrupt handler40Plan
- CVE-2026-74280crypto: marvell/octeontx - fix DMA cleanup using wrong loop index40Plan
- CVE-2026-74279crypto: cavium/cpt - fix DMA cleanup using wrong loop index40Plan
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 | 1a1ebdcb56ae58a0ee2c54dd15d75121e30424e3 | Vendor (CNA) |
| Linux Linux | 3e6473a4f0596182acdda5219b4bebfbee76514f | Vendor (CNA) |
| Linux Linux | 4.20 | Vendor (CNA) |
| Linux Linux | 416095e9a6037b4b39fcadd0d2bd77a8852211ec | Vendor (CNA) |
| Linux Linux | 46d8b8c85ae0589fb85746a64e8908160e52aac3 | Vendor (CNA) |
| Linux Linux | 5.10.261 | Vendor (CNA) |
| Linux Linux | 5.15.212 | Vendor (CNA) |
| Linux Linux | 5.5 | Vendor (CNA) |
| Linux Linux | 5a7ca028facf04921b2c1c2e4d1ee7f282510555 | Vendor (CNA) |
| Linux Linux | 6.1.178 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 6.8 | Vendor (CNA) |
| Linux Linux | 75eb2173b63ab41c24d80cd641af18f3c117a267 | Vendor (CNA) |
| Linux Linux | e2cc711a9df37f359159b21db56cea9c21f58a9c | Vendor (CNA) |
| Linux Linux | ec2612b8ad9e642596db011dd8b6568ef1edeaa1 | Vendor (CNA) |
| azl3 kernel 6.6.143.1-1 on Azure Linux 3.0 | 6.6.150.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.180-1 · 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.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- git.kernel.org/stable/c/1a1ebdcb56ae58a0ee2c54dd15d75121e30424e3
- git.kernel.org/stable/c/3e6473a4f0596182acdda5219b4bebfbee76514f
- git.kernel.org/stable/c/416095e9a6037b4b39fcadd0d2bd77a8852211ec
- git.kernel.org/stable/c/46d8b8c85ae0589fb85746a64e8908160e52aac3
- git.kernel.org/stable/c/5a7ca028facf04921b2c1c2e4d1ee7f282510555
- git.kernel.org/stable/c/75eb2173b63ab41c24d80cd641af18f3c117a267
- git.kernel.org/stable/c/e2cc711a9df37f359159b21db56cea9c21f58a9c
- git.kernel.org/stable/c/ec2612b8ad9e642596db011dd8b6568ef1edeaa1
Vendor advisories and official records. Exploit/PoC links are deliberately left out.