CVE-2026-93189

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 — 3 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: core: quiesce input in hid_hw_stop() to prevent use-after-free

A driver's probe calls hid_device_io_start() to enable input delivery, then fails at a later initialization step and unwinds via hid_hw_stop(). The unwind frees struct hidraw via hidraw_disconnect() while in-flight HID reports may still be running on another CPU, dereferencing the freed object through hidraw_report_event(). syzbot reports the resulting use-after-free for the corsair-psu HID driver.

Edward Adam Davis posted a per-driver fix for corsair-psu that adds an explicit hid_device_io_stop() before hid_hw_stop() in the probe error path ("hwmon: prevent packets from going to driver for probe", 2026-04-28). Auditing the tree shows 15 drivers call hid_device_io_start(); 7 also call hid_device_io_stop() and 8 do not:

drivers calling hid_device_io_start() without a matching hid_device_io_stop() before hid_hw_stop(): drivers/hwmon/corsair-psu.c (fix posted by Edward) drivers/hwmon/corsair-cpro.c drivers/hwmon/nzxt-kraken3.c drivers/hwmon/nzxt-smart2.c drivers/hwmon/gigabyte_waterforce.c drivers/hid/hid-logitech-dj.c drivers/hid/hid-nintendo.c drivers/hid/hid-mcp2221.c

Roughly half of all callers of the API are exposed. Centralize the quiesce in hid_hw_stop() so callers do not have to remember the matching stop: if a driver has left hdev->io_started true on entry, call hid_device_io_stop() before hid_disconnect().

For the 7 drivers that already call hid_device_io_stop() correctly, hdev->io_started is false on entry, the guard short-circuits, and behavior is unchanged.

No Fixes: tag because the affected drivers gained their hid_device_io_start() calls independently over years; the bug is a class-wide API misuse rather than a regression from one commit.

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: core: quiesce input in hid_hw_stop() to prevent use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: core: quiesce input in hid_hw_stop() to prevent use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0fecd89f979a8653b9a5b0816570329b7a94a081
generic

HID: core: quiesce input in hid_hw_stop() to prevent use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/544ebb25bd58f67e821573412ab7a982b9e02211
generic

HID: core: quiesce input in hid_hw_stop() to prevent use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/02246d8b462fd9bd90bc7ae7d6cab1acf69bcb87
generic

HID: core: quiesce input in hid_hw_stop() to prevent use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/92cca302a4eaf65d1b38b3fb600b4ee5eb856a51
generic

HID: core: quiesce input in hid_hw_stop() to prevent use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6787f1828f5616f17250e108c0031fb96fd2cfe6
generic

HID: core: quiesce input in hid_hw_stop() to prevent use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

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

HID: core: quiesce input in hid_hw_stop() to prevent use-after-free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0744cb9520aade37e78f69134f3111086158f1d2

Vendor Advisories for CVE-2026-93189(1)

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 27× in last 7d / 73× 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.

  1. 2026-10-04 23:37 UTCEG score recompute
  2. 2026-10-04 23:37 UTCGHSA enrichment
  3. 2026-10-04 23:22 UTCEPSS rescore
  4. 2026-10-04 12:14 UTCGHSA enrichment
  5. 2026-10-04 00:51 UTCEG score recompute
  6. 2026-10-04 00:51 UTCGHSA enrichment
  7. 2026-10-03 13:29 UTCGHSA enrichment
  8. 2026-10-03 02:06 UTCEG score recompute
  9. 2026-10-03 02:05 UTCGHSA enrichment
  10. 2026-10-02 14:42 UTCGHSA enrichment
  11. 2026-10-02 03:20 UTCEG score recompute
  12. 2026-10-02 03:20 UTCGHSA enrichment
  13. 2026-10-01 19:51 UTCEPSS rescore
  14. 2026-10-01 15:57 UTCGHSA enrichment
  15. 2026-10-01 04:34 UTCGHSA enrichment
  16. 2026-09-30 17:10 UTCEG score recompute
  17. 2026-09-30 17:10 UTCGHSA enrichment
  18. 2026-09-30 15:04 UTCEPSS rescore
  19. 2026-09-30 05:47 UTCGHSA enrichment
  20. 2026-09-29 18:21 UTCEG score recompute
  21. 2026-09-29 18:21 UTCGHSA enrichment
  22. 2026-09-29 06:12 UTCEG score recompute
  23. 2026-09-29 06:12 UTCGHSA enrichment
  24. 2026-09-28 18:50 UTCEG score recompute
  25. 2026-09-28 18:50 UTCGHSA enrichment
Show 48 more
  1. 2026-09-28 13:52 UTCEPSS rescore
  2. 2026-09-28 13:52 UTCEPSS rescore
  3. 2026-09-28 07:27 UTCGHSA enrichment
  4. 2026-09-27 20:05 UTCEG score recompute
  5. 2026-09-27 20:05 UTCGHSA enrichment
  6. 2026-09-27 13:49 UTCEPSS rescore
  7. 2026-09-27 08:42 UTCGHSA enrichment
  8. 2026-09-26 21:19 UTCEG score recompute
  9. 2026-09-26 21:19 UTCGHSA enrichment
  10. 2026-09-26 15:59 UTCEPSS rescore
  11. 2026-09-26 09:56 UTCEG score recompute
  12. 2026-09-26 09:56 UTCGHSA enrichment
  13. 2026-09-25 22:30 UTCGHSA enrichment
  14. 2026-09-25 10:22 UTCGHSA enrichment
  15. 2026-09-24 22:59 UTCEG score recompute
  16. 2026-09-24 22:59 UTCGHSA enrichment
  17. 2026-09-24 14:04 UTCEPSS rescore
  18. 2026-09-24 11:05 UTCGHSA enrichment
  19. 2026-09-23 23:42 UTCEG score recompute
  20. 2026-09-23 23:42 UTCGHSA enrichment
  21. 2026-09-23 17:54 UTCEPSS rescore
  22. 2026-09-23 12:20 UTCGHSA enrichment
  23. 2026-09-23 00:58 UTCEG score recompute
  24. 2026-09-23 00:58 UTCGHSA enrichment
  25. 2026-09-22 16:01 UTCEPSS rescore
  26. 2026-09-22 13:35 UTCGHSA enrichment
  27. 2026-09-22 02:13 UTCEG score recompute
  28. 2026-09-22 02:13 UTCGHSA enrichment
  29. 2026-09-21 21:09 UTCEPSS rescore
  30. 2026-09-21 14:49 UTCGHSA enrichment
  31. 2026-09-21 03:21 UTCEG score recompute
  32. 2026-09-21 03:21 UTCGHSA enrichment
  33. 2026-09-20 20:16 UTCEPSS rescore
  34. 2026-09-20 15:58 UTCGHSA enrichment
  35. 2026-09-20 04:35 UTCGHSA enrichment
  36. 2026-09-19 17:12 UTCEG score recompute
  37. 2026-09-19 17:12 UTCGHSA enrichment
  38. 2026-09-19 05:49 UTCEG score recompute
  39. 2026-09-19 05:49 UTCGHSA enrichment
  40. 2026-09-18 19:28 UTCEPSS rescore
  41. 2026-09-18 18:26 UTCEG score recompute
  42. 2026-09-18 18:26 UTCGHSA enrichment
  43. 2026-09-18 18:00 UTCEG score recompute▲ 8.80
  44. 2026-09-18 18:00 UTCGHSA enrichment
  45. 2026-09-18 17:59 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  46. 2026-09-17 17:24 UTCNVD update
  47. 2026-09-17 16:20 UTCEG score recompute
  48. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-93189?
CVE-2026-93189 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: HID: core: quiesce input in hidhwstop() to prevent use-after-free A driver's probe calls hiddeviceio_start() to enable input delivery, then fails at a later initialization step and unwinds via hidhwstop(). The unwind frees struct…
When was CVE-2026-93189 disclosed?
CVE-2026-93189 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-93189 actively exploited?
CVE-2026-93189 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-93189?
CVE-2026-93189 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-93189?
No fix for CVE-2026-93189 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-93189 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-93189

Explore →

Is Your Infrastructure Affected by CVE-2026-93189?

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

Book a Demo →Browse All CVEs