CVE-2026-68091

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-10. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

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.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity88% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
18%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 17, 2026

Advisory Details (8)

Auto-updated Aug 14, 2026
No patch confirmed yet.
generic

HID: wacom: stop hardware after post-start probe failures - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ec2612b8ad9e642596db011dd8b6568ef1edeaa1
generic

HID: wacom: stop hardware after post-start probe failures - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/e2cc711a9df37f359159b21db56cea9c21f58a9c
generic

HID: wacom: stop hardware after post-start probe failures - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/75eb2173b63ab41c24d80cd641af18f3c117a267
generic

HID: wacom: stop hardware after post-start probe failures - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5a7ca028facf04921b2c1c2e4d1ee7f282510555
generic

HID: wacom: stop hardware after post-start probe failures - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/46d8b8c85ae0589fb85746a64e8908160e52aac3
generic

HID: wacom: stop hardware after post-start probe failures - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/416095e9a6037b4b39fcadd0d2bd77a8852211ec
generic

HID: wacom: stop hardware after post-start probe failures - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3e6473a4f0596182acdda5219b4bebfbee76514f
generic

HID: wacom: stop hardware after post-start probe failures - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1a1ebdcb56ae58a0ee2c54dd15d75121e30424e3

Vendor Advisories for CVE-2026-68091(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(5)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)6.1.180-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)6.12.96-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (158 versions)7.1.4-1

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 36× in last 7d / 156× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 204 total refreshes for this CVE.

  1. 2026-09-20 22:46 UTCEG score recompute
  2. 2026-09-20 22:46 UTCVendor advisory
  3. 2026-09-20 22:46 UTCGHSA enrichment
  4. 2026-09-20 20:16 UTCEPSS rescore
  5. 2026-09-20 11:13 UTCVendor advisory
  6. 2026-09-20 11:13 UTCGHSA enrichment
  7. 2026-09-19 23:59 UTCEG score recompute
  8. 2026-09-19 23:59 UTCVendor advisory
  9. 2026-09-19 23:59 UTCGHSA enrichment
  10. 2026-09-19 12:44 UTCVendor advisory
  11. 2026-09-19 12:44 UTCGHSA enrichment
  12. 2026-09-19 00:53 UTCEG score recompute
  13. 2026-09-19 00:53 UTCVendor advisory
  14. 2026-09-19 00:53 UTCGHSA enrichment
  15. 2026-09-18 19:28 UTCEPSS rescore
  16. 2026-09-18 13:34 UTCVendor advisory
  17. 2026-09-18 13:34 UTCGHSA enrichment
  18. 2026-09-18 02:19 UTCEG score recompute
  19. 2026-09-18 02:19 UTCVendor advisory
  20. 2026-09-18 02:19 UTCGHSA enrichment
  21. 2026-09-17 15:04 UTCVendor advisory
  22. 2026-09-17 15:04 UTCGHSA enrichment
  23. 2026-09-17 00:50 UTCEG score recompute
  24. 2026-09-17 00:50 UTCVendor advisory
  25. 2026-09-17 00:50 UTCGHSA enrichment
Show 75 more
  1. 2026-09-16 14:08 UTCEPSS rescore
  2. 2026-09-16 05:15 UTCEPSS rescore
  3. 2026-09-16 02:39 UTCVendor advisory
  4. 2026-09-16 02:39 UTCGHSA enrichment
  5. 2026-09-15 14:05 UTCEG score recompute
  6. 2026-09-15 14:05 UTCVendor advisory
  7. 2026-09-15 14:05 UTCGHSA enrichment
  8. 2026-09-15 00:45 UTCVendor advisory
  9. 2026-09-15 00:45 UTCGHSA enrichment
  10. 2026-09-14 11:19 UTCVendor advisory
  11. 2026-09-14 11:19 UTCGHSA enrichment
  12. 2026-09-14 00:04 UTCEG score recompute
  13. 2026-09-14 00:04 UTCVendor advisory
  14. 2026-09-14 00:04 UTCGHSA enrichment
  15. 2026-09-13 12:50 UTCVendor advisory
  16. 2026-09-13 12:50 UTCGHSA enrichment
  17. 2026-09-13 01:35 UTCEG score recompute
  18. 2026-09-13 01:35 UTCVendor advisory
  19. 2026-09-13 01:35 UTCGHSA enrichment
  20. 2026-09-12 14:20 UTCVendor advisory
  21. 2026-09-12 14:20 UTCGHSA enrichment
  22. 2026-09-12 03:05 UTCVendor advisory
  23. 2026-09-12 03:05 UTCGHSA enrichment
  24. 2026-09-11 15:50 UTCEG score recompute
  25. 2026-09-11 15:50 UTCVendor advisory
  26. 2026-09-11 15:50 UTCGHSA enrichment
  27. 2026-09-11 14:53 UTCEPSS rescore
  28. 2026-09-11 09:37 UTCEPSS rescore
  29. 2026-09-11 04:35 UTCVendor advisory
  30. 2026-09-11 04:35 UTCGHSA enrichment
  31. 2026-09-10 17:12 UTCEG score recompute
  32. 2026-09-10 17:11 UTCGHSA enrichment
  33. 2026-09-10 05:49 UTCVendor advisory
  34. 2026-09-10 05:49 UTCGHSA enrichment
  35. 2026-09-09 18:34 UTCEG score recompute
  36. 2026-09-09 18:34 UTCVendor advisory
  37. 2026-09-09 18:34 UTCGHSA enrichment
  38. 2026-09-09 05:55 UTCEG score recompute
  39. 2026-09-09 05:55 UTCVendor advisory
  40. 2026-09-09 05:55 UTCGHSA enrichment
  41. 2026-09-08 22:01 UTCEPSS rescore
  42. 2026-09-08 04:43 UTCVendor advisory
  43. 2026-09-08 04:43 UTCGHSA enrichment
  44. 2026-09-07 17:28 UTCEG score recompute
  45. 2026-09-07 17:28 UTCVendor advisory
  46. 2026-09-07 17:28 UTCGHSA enrichment
  47. 2026-09-07 16:01 UTCEPSS rescore
  48. 2026-09-06 14:19 UTCEG score recompute
  49. 2026-09-06 14:19 UTCVendor advisory
  50. 2026-09-06 14:19 UTCGHSA enrichment
  51. 2026-09-06 13:47 UTCEPSS rescore
  52. 2026-09-06 03:05 UTCVendor advisory
  53. 2026-09-06 03:05 UTCGHSA enrichment
  54. 2026-09-05 15:50 UTCEG score recompute
  55. 2026-09-05 15:50 UTCVendor advisory
  56. 2026-09-05 15:50 UTCGHSA enrichment
  57. 2026-09-05 15:31 UTCEPSS rescore
  58. 2026-09-05 02:10 UTCEG score recompute
  59. 2026-09-05 02:10 UTCVendor advisory
  60. 2026-09-05 02:10 UTCGHSA enrichment
  61. 2026-09-04 08:27 UTCEG score recompute
  62. 2026-09-04 08:27 UTCVendor advisory
  63. 2026-09-04 08:27 UTCGHSA enrichment
  64. 2026-09-04 05:07 UTCEPSS rescore
  65. 2026-09-03 17:05 UTCVendor advisory
  66. 2026-09-03 17:05 UTCGHSA enrichment
  67. 2026-09-03 02:59 UTCEG score recompute
  68. 2026-09-03 02:59 UTCVendor advisory
  69. 2026-09-03 02:59 UTCGHSA enrichment
  70. 2026-09-02 14:12 UTCEPSS rescore
  71. 2026-09-02 06:35 UTCVendor advisory
  72. 2026-09-02 06:35 UTCGHSA enrichment
  73. 2026-09-01 17:20 UTCEG score recompute
  74. 2026-09-01 17:20 UTCVendor advisory
  75. 2026-09-01 17:20 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-68091?
CVE-2026-68091 is a high vulnerability published on August 10, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: wacom: stop hardware after post-start probe failures wacomparseand_register() starts HID hardware before registering inputs and initializing pad LEDs/remotes. Those later steps can fail, but their error paths currently release…
When was CVE-2026-68091 disclosed?
CVE-2026-68091 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-68091 actively exploited?
CVE-2026-68091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 81.6% of all scored CVEs.
What is the CVSS score of CVE-2026-68091?
CVE-2026-68091 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-68091?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-68091, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-68091

Explore →

Is Your Infrastructure Affected by CVE-2026-68091?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.