CVE-2026-68091

HIGHPre-NVD 8.88.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-55272 (ENISA EUVD) · GHSA-jmfj-p2w9-43g4 (GitHub Security Advisories)Source: ENISA EUVD

8.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.8Exploit: None knownExposed services: Not assessed

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.8HIGHmedium confidence
EG Risk
40
EG Risk 40/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity88% × 45%
Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.3% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.

EG Severity
8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 10, 2026

Last Modified

October 19, 2026

Advisory Details (8)

Auto-updated Aug 14, 2026
Patch available.
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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
Web page

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(28)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18) @ resolute2026-11-18ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-11-18ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1018.18~24.04.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-11-18ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-11-18ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-11-18ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-11-18ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1019.19) @ resolute2026-11-18ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1113.111) @ jammy2026-11-18ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2018.18) @ resolute2026-11-18ubuntu
ubuntulinux-tools-ibm-7.0 (7.0.0-1013.13) @ resolute2026-11-18ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1011.11~24.04.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1036.39) @ noble2026-11-18ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-11-18ubuntu
ubuntulinux-tools-nvidia-tegra-rt-5.15 (5.15.0.1070.72~20.04.1) @ focal2026-11-18ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2056.58) @ noble2026-11-18ubuntu
ubuntulinux-tools-azure-edge (7.0.0-1014.14~24.04.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-11-18ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1067.70) @ noble2026-11-18ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-31.31~24.04.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-11-18ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1011.11) @ resolute2026-11-18ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-149.149~22.04.1) @ jammy2026-11-18ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1071.78~22.04.1) @ jammy2026-11-18ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-11-18ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-11-18ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1067.70.1) @ noble2026-11-18ubuntu
linuxKernel @ 4.20 (fixes >=4.19.307)—osv

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions)
  • every version up to 6.12.96-1: fixed in 6.12.96-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.4-1: fixed in 7.1.4-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(24)

Data Freshness Timeline

(refreshed 10× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 350 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 250 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-21 22:26 UTCOSV refresh
  2. 2026-11-21 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  3. 2026-11-20 16:38 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  4. 2026-11-19 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-11-18 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-11-18 09:06 UTCEchelonGraph re-scored
  7. 2026-11-18 09:06 UTCVendor advisory
  8. 2026-11-18 09:06 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  9. 2026-11-17 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-11-16 16:52 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-11-15 17:01 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  12. 2026-11-14 16:41 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  13. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-11-11 05:02 UTCEchelonGraph re-scored
  17. 2026-11-11 05:02 UTCVendor advisory
  18. 2026-11-11 05:02 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  19. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  20. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  21. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  22. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  23. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  24. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  25. 2026-11-04 16:36 UTCEPSS rescoreEPSS 0.3% · 18th percentile
Show 75 more
  1. 2026-11-03 23:48 UTCEchelonGraph re-scored
  2. 2026-11-03 23:48 UTCVendor advisory
  3. 2026-11-03 23:48 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  4. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  8. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  9. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  10. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  11. 2026-10-27 19:14 UTCEchelonGraph re-scored
  12. 2026-10-27 19:14 UTCVendor advisory
  13. 2026-10-27 19:14 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  14. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  17. 2026-10-25 14:10 UTCEchelonGraph re-scored
  18. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  19. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  20. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  21. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.3% · 17th percentile
  22. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  23. 2026-10-19 21:42 UTCEchelonGraph re-scored
  24. 2026-10-19 21:42 UTCVendor advisory
  25. 2026-10-19 21:41 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  26. 2026-10-19 20:54 UTCEchelonGraph re-scored
  27. 2026-10-19 20:54 UTCVendor advisory
  28. 2026-10-19 20:53 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  29. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  30. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  31. 2026-10-18 03:20 UTCEchelonGraph re-scored
  32. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  33. 2026-10-16 17:35 UTCEchelonGraph re-scored
  34. 2026-10-16 17:35 UTCVendor advisory
  35. 2026-10-16 17:35 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  36. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  37. 2026-10-16 16:09 UTCEchelonGraph re-scored
  38. 2026-10-16 16:09 UTCVendor advisory
  39. 2026-10-16 16:08 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  40. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  41. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.3% · 16th percentile
  42. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  43. 2026-10-13 10:17 UTCEchelonGraph re-scored
  44. 2026-10-13 10:17 UTCVendor advisory
  45. 2026-10-13 10:17 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  46. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  47. 2026-10-12 15:45 UTCEchelonGraph re-scored
  48. 2026-10-11 19:30 UTCEchelonGraph re-scored
  49. 2026-10-11 16:45 UTCEchelonGraph re-scored
  50. 2026-10-11 14:06 UTCEchelonGraph re-scored
  51. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  52. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  53. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  54. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  55. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  56. 2026-10-07 06:10 UTCVendor advisory
  57. 2026-10-07 06:10 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  58. 2026-10-06 18:52 UTCEchelonGraph re-scored
  59. 2026-10-06 18:52 UTCVendor advisory
  60. 2026-10-06 18:52 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  61. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  62. 2026-10-05 19:28 UTCEchelonGraph re-scored
  63. 2026-10-05 19:28 UTCVendor advisory
  64. 2026-10-05 19:28 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  65. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  66. 2026-10-05 07:53 UTCEchelonGraph re-scored
  67. 2026-10-05 07:53 UTCVendor advisory
  68. 2026-10-05 07:53 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  69. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  70. 2026-10-04 16:44 UTCVendor advisory
  71. 2026-10-04 16:44 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  72. 2026-10-04 05:29 UTCEchelonGraph re-scored
  73. 2026-10-04 05:29 UTCVendor advisory
  74. 2026-10-04 05:28 UTCGHSA enrichmentGHSA-jmfj-p2w9-43g4 · GitHub severity HIGH · GitHub CVSS 8.8
  75. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.4% · 33rd percentile

Frequently asked(5)

What is CVE-2026-68091?
CVE-2026-68091 is a high-severity vulnerability; its CVE record was published on August 10, 2026. 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…
When was the CVE record for CVE-2026-68091 published?
The CVE record for CVE-2026-68091 was published on August 10, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-68091 actively exploited?
CVE-2026-68091 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-68091?
CVE-2026-68091 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-68091?
A fix for CVE-2026-68091 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-68091 are linked in the Vendor Advisories panel on this page.

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.