CVE-2026-90227

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
7.8EG
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.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:

nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed()

Unlike IO_CMD / IO64_CMD, NVME_IOCTL_SUBMIT_IO never calls nvme_cmd_allowed(). Unprivileged callers can thus issue I/O on a partition device or write through a read-only file descriptor.

Pass flags and open_for_write through and reject disallowed commands with -EACCES.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/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
Severity78% × 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
6th
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 (5)

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

nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/95b0591d51dbf9e618d7845883d535e88ad7c8af
generic

nvme/ioctl: check SUBMIT_IO with nvme_cmd_allowed() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/736b7c6adc7a65c4411beff197b6a634f7a6ca27

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

Frequently asked(5)

What is CVE-2026-90227?
CVE-2026-90227 is a high vulnerability published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme/ioctl: check SUBMITIO with nvmecmd_allowed() Unlike IOCMD / IO64CMD, NVMEIOCTLSUBMIT_IO never calls nvmecmdallowed(). Unprivileged callers can thus issue I/O on a partition device or write through a read-only file descriptor.…
When was CVE-2026-90227 disclosed?
CVE-2026-90227 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-90227 actively exploited?
CVE-2026-90227 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90227?
CVE-2026-90227 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90227?
No fix for CVE-2026-90227 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-90227 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-90227

Explore →

Is Your Infrastructure Affected by CVE-2026-90227?

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