CVE-2026-90229

HIGHPre-NVD 7.47.4
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-81822 (ENISA EUVD) · GHSA-mcwm-v4jq-wq65 (GitHub Security Advisories)Source: ENISA EUVD

7.4EG
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.2%CVSS: 7.4Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

nvme-apple: Destroy the admin queue on removal

The admin queue is allocated with blk_mq_alloc_queue() but never destroyed. nvme_free_ctrl() only drops the last reference and blk_mq_exit_queue() and blk_sync_queue() never run: the hctx is never moved to q->unused_hctx_list and the timeout timer and work stay armed on a queue that is about to be freed which will eventually oops inside blk_mq_timeout_work().

This can only be triggered when the controller fails to come up and is then immediately torn down again which is why no one ever ran into this before.

Let's just copy what the pcie driver does: unquiesce and destroy the admin queue before nvme_uninit_ctrl().

With this the following WARN followed by a panic no longer happens:

WARNING: block/blk-mq.c:4390 at blk_mq_release+0x194/0x238, CPU#4: kworker/u34:4/119 CPU: 4 UID: 0 PID: 119 Comm: kworker/u34:4 Not tainted 7.2.0-rc1-dirty #248 PREEMPT Hardware name: Apple Mac mini (M1, 2020) (DT) Workqueue: nvme-wq apple_nvme_remove_dead_ctrl_work pstate: 61400005 (nZCv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) pc : blk_mq_release+0x194/0x238 lr : blk_mq_release+0x58/0x238 sp : ffffc000833a3b50 x29: ffffc000833a3b50 x28: ffff80001d0450f8 x27: ffff800020c95200 x26: 0000000000000088 x25: 0000000000000000 x24: ffff800020f36805 x23: 0000000000000000 x22: ffffc00081a86878 x21: ffff800020be9c60 x20: 0000000000000000 x19: ffff800022501698 x18: 000000000000000a x17: 7365757165722066 x16: 666f7265776f7020 x15: 0000000000000000 x14: 0000000000000028 x13: 0000000000004def x12: 0000000000000003 x11: 0000000000000000 x10: 0000000000000000 x9 : ffffc000805b4fc8 x8 : ffffc00081915820 x7 : ffffc00081c4f3c8 x6 : 0000000000000001 x5 : 0000000000000004 x4 : ffff800022498d80 x3 : ffffc000833a3b14 x2 : 0000000000000000 x1 : 0000000000000000 x0 : ffff800022501698 Call trace: blk_mq_release+0x194/0x238 (P) blk_put_queue+0x8c/0xf0 nvme_free_ctrl+0x4c/0x260 device_release+0x44/0x128 kobject_put+0xa0/0x120 put_device+0x1c/0x40 nvme_uninit_ctrl+0x48/0x60 apple_nvme_remove+0x54/0xb0 platform_remove+0x28/0x40 device_remove+0x54/0x98 device_release_driver_internal+ device_release_driver+0x20/0x38 apple_nvme_remove_dead_ctrl_wor process_one_work+0x1f4/0x770 worker_thread+0x1b8/0x360 kthread+0x140/0x160 ret_from_fork+0x10/0x20 irq event stamp: 448 hardirqs last enabled at (447):in_unlock_irqrestore+0x74/0x80 hardirqs last disabled at (448): [] el1_brk64+0x20/0x60 softirqs last enabled at (0): [ess+0xb28/0x2698 softirqs last disabled at (0): [<0000000000000000>] 0x0 ---[ end trace 0000000000000000 Unable to handle kernel NULL pointer dereference at virtual address 0000000000000000 Mem abort info: ESR = 0x0000000096000005 EC = 0x25: DABT (current EL), SET = 0, FnV = 0 EA = 0, S1PTW = 0 FSC = 0x05: level 1 translation fault Data abort info: ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000 CM = 0, WnR = 0, TnD = 0, TagA GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0 [0000000000000000] user address Internal error: Oops: 0000000096000005 [#1] SMP CPU: 7 UID: 0 PID: 54 Comm: kwor 7.2.0-rc1-dirty #248PREEMPT Tainted: [W]=WARN Hardware name: Apple Mac mini (M1, 2020) (DT) Workqueue: kblockd blk_mq_timeou pstate: 01400005 (nzcv daif +PAN -UAO -TCO +DIT -SSBS BTYPE=--) pc : percpu_ref_tryget_many.cons lr : percpu_ref_tryget_many.constprop.0+0xc0/0x168 sp : ffffc000829cbce0 x29: ffffc000829cbce0 x28: ffff800020be9f48 x27: ffff800013e503c0 x26: 0000000000000108 x25: 000009c05 x23: 0000000000000000 x22: ffffc000819f5000 x21: ffff800020be9f48 x20: ffff8001deda4808 x19: ffff8000a x17: 00000000580e1fac x16: ffffc00082bbbb7c x15: 0000000000000000 x14: 0000000000000028 x13: 000000001 x11: 0000000000000000 x10: 0000000000000000 x9 : ffffc000829cbc20 x8 : ---truncated---

CVSS v3
7.4
EG Score
7.4HIGHmedium confidence
EG Risk
33
EG Risk 33/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)
Severity74% × 45%
Impact severity (EG Severity): CVSS 7.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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.2%
EPSS %ILE
6th
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 (7.4): severity, escalated by confirmed exploitation. This CVE's 7.4 is its impact severity (EG Severity), not escalated.

EG Severity
7.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-13). 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 (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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

September 17, 2026

Last Modified

October 30, 2026

Advisory Details (5)

Auto-updated Sep 18, 2026
Patch available.
Web page

nvme-apple: Destroy the admin queue on removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c11685ee4eedc70f738b117a4a8c0fbe84cd79b3
Web page

nvme-apple: Destroy the admin queue on removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bf51e306e3dcffd1a63ef09a7a39d28f3578dd2d
Web page

nvme-apple: Destroy the admin queue on removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/87d5b9864c8118d26f54de4b66d2bddf2c659272
Web page

nvme-apple: Destroy the admin queue on removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5f6f4777b7a8676251139dbfbcdec3cb578f0e40
Web page

nvme-apple: Destroy the admin queue on removal - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/215d1682f0bae495f3f9cf692b358116b7a18602

Vendor Advisories for CVE-2026-90229(2)

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

Patch Availability(13)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-42.42) @ resolute2026-11-13ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1071.78~22.04.1) @ jammy2026-11-13ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1017.17) @ resolute2026-11-13ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1016.18~24.04.1) @ noble2026-11-13ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1039.40) @ noble2026-11-13ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1067.70.1) @ noble2026-11-13ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1020.21) @ resolute2026-11-13ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2056.58) @ noble2026-11-13ubuntu
ubuntulinux-tools-realtime-6.8.1 (6.8.1-1064.65) @ noble2026-11-13ubuntu
ubuntulinux-vmware-tools-6.8.0-1010 (6.8.0-1010.10) @ noble2026-11-13ubuntu
ubuntulinux-tools-nvidia-64k-6.8 (6.8.0-1067.70) @ noble2026-11-13ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-149.149~22.04.1) @ jammy2026-11-13ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1071.78) @ noble2026-11-13ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 3 ecosystems)
Debian:12(2)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 7.3~rc7-1~exp1 (371 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 (180 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 46× 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 204 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 104 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-90229?
CVE-2026-90229 is a high-severity vulnerability; its CVE record was published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme-apple: Destroy the admin queue on removal The admin queue is allocated with blk_mq_alloc_queue() but never destroyed. nvme_free_ctrl() only drops the last reference and blk_mq_exit_queue() and blk_sync_queue() never run: the…
When was the CVE record for CVE-2026-90229 published?
The CVE record for CVE-2026-90229 was published on September 17, 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 30, 2026; the record at its source may have been updated since.
Is CVE-2026-90229 actively exploited?
CVE-2026-90229 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-90229?
CVE-2026-90229 has a CVSS base score of 7.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-90229?
A fix for CVE-2026-90229 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90229 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-90229

Explore →

Is Your Infrastructure Affected by CVE-2026-90229?

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

Book a Demo →Browse All CVEs