CVE-2026-93054

HIGHPre-NVD 7.07.0—
EchelonGraph scoreHIGH confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. A secondary CVSS source baseline 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.0EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.0Exploit: 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:

uio: Fix stale info pointer in failed registration path

After device_add(), the UIO device is visible to userspace and /dev/uioX can be opened. If a later setup step fails, __uio_register_device() unwinds the device but leaves idev->info pointing at the caller-owned struct uio_info.

That is unsafe when an opener races with the failed registration path. The open file keeps a reference to the uio_device, while the caller sees registration failure and may free its struct uio_info. Later file operations can then follow idev->info and dereference freed memory.

Handle post-device_add() failures like unregister: remove UIO attributes while the info pointer is still valid, then clear idev->info under info_lock and wake existing waiters/async users before removing the device and minor. This makes already-open file descriptors observe the same "device gone" state as normal uio_unregister_device().

CVSS v3
7.0
EG Score
7.0HIGHhigh confidence
EG Risk
36
EG Risk 36/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
Severity70% × 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.2%
EPSS %ILE
4th
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

uio: Fix stale info pointer in failed registration path - kernel/git/stable/linux.git - Linux kernel stable tree

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

uio: Fix stale info pointer in failed registration path - kernel/git/stable/linux.git - Linux kernel stable tree

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

uio: Fix stale info pointer in failed registration path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/67b6fc084b034a91c3ec7907a3fed89a2450f30b
generic

uio: Fix stale info pointer in failed registration path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63eaa7663335d482a8825c231213e312cacea567
generic

uio: Fix stale info pointer in failed registration path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/506b43dde5f9ac0068b1360e6b5dbee07fda59fb
generic

uio: Fix stale info pointer in failed registration path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/234156f6c6d9ec35dc47abbcc3adc3c79fc6a5ac
generic

uio: Fix stale info pointer in failed registration path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/16695e9059d80ea6661e8399064b0c01f641dd8c
generic

uio: Fix stale info pointer in failed registration path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15340b00e665af805523b08515294a1aa1778151

Vendor Advisories for CVE-2026-93054(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 39× in last 7d / 102× 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 102 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-93054?
CVE-2026-93054 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: uio: Fix stale info pointer in failed registration path After device_add(), the UIO device is visible to userspace and /dev/uioX can be opened. If a later setup step fails, uioregisterdevice() unwinds the device but leaves…
When was CVE-2026-93054 disclosed?
CVE-2026-93054 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-93054 actively exploited?
CVE-2026-93054 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-93054?
CVE-2026-93054 has a CVSS base score of 7.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-93054?
No fix for CVE-2026-93054 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-93054 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-93054

Explore →

Is Your Infrastructure Affected by CVE-2026-93054?

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

Book a Demo →Browse All CVEs