CVE-2026-90329

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. 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 mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 8.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.8
EG Score
8.8HIGHhigh confidence
EG Risk
44
EG Risk 44/100CISA SSVC

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%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.4%
EPSS %ILE
31st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (8)

Auto-updated Sep 18, 2026
No patch confirmed yet.
generic

HID: synchronize input before cleaning up a failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/207853d46f7ef2e28042344a1468da8754c3ddbf
generic

HID: synchronize input before cleaning up a failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: synchronize input before cleaning up a failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/01eeb601a1626e683fb7b77c63f442b06fb87093
generic

HID: synchronize input before cleaning up a failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: synchronize input before cleaning up a failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9a3da56aae28e1ad3a3e591f72a537742053ecd2
generic

HID: synchronize input before cleaning up a failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/98201b46f7e33fe11af6f024fecb40fb56634225
generic

HID: synchronize input before cleaning up a failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2c35cdeb13a0c52429501e66f368fa59cad235f6
generic

HID: synchronize input before cleaning up a failed probe - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3ffb088a2ed34ca982cfc2c81d107ce370aa45f1

Vendor Advisories for CVE-2026-90329(2)

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

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.2~rc7-1~exp1 (360 versions)
  • every version on: no fix on record
—
linux-6.126.12.100-1~deb12u1, 6.12.101-1~deb12u1, 6.12.107-1~deb12u1
  • every version up to 6.12.111-1~deb12u1: fixed in 6.12.111-1~deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (35 versions)
  • every version up to 6.12.111-1: fixed in 6.12.111-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Data Freshness Timeline

(refreshed 41× in last 7d / 104× 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 104 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-90329?
CVE-2026-90329 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: synchronize input before cleaning up a failed probe hiddeviceio_start() allows reports to run concurrently with probe. If the probe subsequently fails, hiddeviceprobe() releases driver resources and clears hdev->driver without…
When was CVE-2026-90329 disclosed?
CVE-2026-90329 was first published on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-90329 actively exploited?
CVE-2026-90329 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (31st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90329?
CVE-2026-90329 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-90329?
No fix for CVE-2026-90329 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-90329 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-90329

Explore →

Is Your Infrastructure Affected by CVE-2026-90329?

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