CVE-2026-68091 — 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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
version dbaca8fa9ec2c5aa55ec515686ce3b9007554eabversion 6.8≥ 6.7.6 and < 6.8≥ 5.4.269 and < 5.5≥ 4.19.307 and < 4.20≥ 6.6.18 and < 6.6.145≥ 6.1.79 and < 6.1.178≥ 5.15.149 and < 5.15.212 and 11 more≥ 5.10.210 and < 5.10.261version 79187e8099a9feb550916dbfb962497522022b6d≥ f304eb483393f135ab479d02da6f5dc7d9b51cd6 and < 5a7ca028facf04921b2c1c2e4d1ee7f282510555version d943536197c1a05e377452af4ec7942e11d018f4≥ c1d6708bf0d3dd976460d435373cf5abf21ce258 and < ec2612b8ad9e642596db011dd8b6568ef1edeaa1≥ c1d6708bf0d3dd976460d435373cf5abf21ce258 and < e2cc711a9df37f359159b21db56cea9c21f58a9c≥ c1d6708bf0d3dd976460d435373cf5abf21ce258 and < 416095e9a6037b4b39fcadd0d2bd77a8852211ec≥ c1d6708bf0d3dd976460d435373cf5abf21ce258 and < 75eb2173b63ab41c24d80cd641af18f3c117a267≥ fc41101a94b11cd0d5ad8e213b2b6965f248d653 and < 1a1ebdcb56ae58a0ee2c54dd15d75121e30424e3≥ e5c6c8ef3e4d3a88407404daafbf2c6be62f2185 and < 46d8b8c85ae0589fb85746a64e8908160e52aac3≥ 853307924a9003b3142b5253b1caa6625fbad9fc and < 3e6473a4f0596182acdda5219b4bebfbee76514f |
Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | 416baaa9-dc9f-4396-8d5f-8c081fb06d67 via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | Linux via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H (score shown at the top: 416baaa9-dc9f-4396-8d5f-8c081fb06d67) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · linux/linux
- Record published
- CVSS changed · 8.8
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/75eb2173b63ab41c24d80cd641af18f3c117a267
- git.kernel.org/stable/c/46d8b8c85ae0589fb85746a64e8908160e52aac3
- git.kernel.org/stable/c/416095e9a6037b4b39fcadd0d2bd77a8852211ec
- git.kernel.org/stable/c/e2cc711a9df37f359159b21db56cea9c21f58a9c
- git.kernel.org/stable/c/ec2612b8ad9e642596db011dd8b6568ef1edeaa1
- git.kernel.org/stable/c/3e6473a4f0596182acdda5219b4bebfbee76514f
- git.kernel.org/stable/c/1a1ebdcb56ae58a0ee2c54dd15d75121e30424e3
- git.kernel.org/stable/c/5a7ca028facf04921b2c1c2e4d1ee7f282510555
Elsewhere on this site
Related CVEs (same products)
- Critical CVE-2026-99999 ipv4: validate checksum_start before completing checksum 11h
- Unknown CVE-2026-98432 ipv4: free inet_opt and ireq_opt after an RCU grace period 11h
- Unknown CVE-2026-98424 wifi: cfg80211: undo netns switch if renaming the wiphy fails 1d
- Unknown CVE-2026-98425 wifi: mac80211: don't warn when an IBSS has no channel to scan 1d
- Unknown CVE-2026-98426 wifi: mwifiex: fix IRQ leak using wrong index in MSI-X error path 1d
- Unknown CVE-2026-98427 net/sched: codel: bound the dropping loop per dequeue call 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-68091 is "HID: wacom: stop hardware after post-start probe failures", rated High. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.