CVE-2026-74384

CRITICALPre-NVD 9.89.8
EchelonGraph scoreMEDIUM confidence

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

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-08-15. A secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this week

Also known asEUVD-2026-59531 (ENISA EUVD) · GHSA-hggw-gjv7-4223 (GitHub Security Advisories)Source: ENISA EUVD

9.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 9.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

nvme-multipath: fix flex array size in struct nvme_ns_head

struct nvme_ns_head contains a flexible array member, current_path[], which is indexed using the NUMA node ID: head->current_path[numa_node_id()]

The structure is currently allocated as: size = sizeof(struct nvme_ns_head) + (num_possible_nodes() * sizeof(struct nvme_ns *)); head = kzalloc(size, GFP_KERNEL);

This allocation assumes that NUMA node IDs are sequential and densely packed from 0 .. num_possible_nodes() - 1. While this assumption holds on many systems, it is not always true on some architectures such as powerpc.

On some powerpc systems, NUMA node IDs can be sparse. For example: NUMA: NUMA node(s): 6 NUMA node0 CPU(s): 80-159 NUMA node8 CPU(s): 0-79 NUMA node252 CPU(s): NUMA node253 CPU(s): NUMA node254 CPU(s): NUMA node255 CPU(s):

That is, the possible/online NUMA node IDs are: 0, 8, 252, 253, 254, 255 In this case: num_possible_nodes() = 6

So memory is allocated for only 6 entries in current_path[]. However, the array is later indexed using the actual NUMA node ID. As a result, accesses such as: head->current_path[8] or head->current_path[252] goes out of bounds, leading to the following KASAN splat:

================================================================== BUG: KASAN: slab-out-of-bounds in nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core] Write of size 8 at addr c00020003bda35b8 by task kworker/u641:2/1997

CPU: 1 UID: 0 PID: 1997 Comm: kworker/u641:2 Not tainted 7.1.0-rc5-dirty #14 PREEMPT(lazy) Hardware name: 8335-GTH POWER9 0x4e1202 opal:skiboot-v6.5.3-35-g1851b2a06 PowerNV Workqueue: async async_run_entry_fn Call Trace: [c000200037fa7510] [c0000000021c23d4] dump_stack_lvl+0x88/0xdc (unreliable) [c000200037fa7540] [c0000000009fda90] print_report+0x22c/0x67c [c000200037fa7630] [c0000000009fd508] kasan_report+0x108/0x220 [c000200037fa7740] [c0000000009fff48] __asan_store8+0xe8/0x120 [c000200037fa7760] [c008000018e76474] nvme_mpath_revalidate_paths+0x22c/0x290 [nvme_core] [c000200037fa7800] [c008000018e6556c] nvme_update_ns_info+0x4a4/0x5e0 [nvme_core] [c000200037fa7a50] [c008000018e66270] nvme_alloc_ns+0x6d8/0x1a70 [nvme_core] [c000200037fa7c20] [c008000018e679fc] nvme_scan_ns+0x3f4/0x630 [nvme_core] [c000200037fa7d10] [c00000000031f22c] async_run_entry_fn+0x9c/0x3a0 [c000200037fa7db0] [c0000000002fa544] process_one_work+0x414/0xa10 [c000200037fa7ec0] [c0000000002fbf00] worker_thread+0x320/0x640 [c000200037fa7f80] [c00000000030d0f8] kthread+0x278/0x290 [c000200037fa7fe0] [c00000000000ded8] start_kernel_thread+0x14/0x18

Allocated by task 1997 on cpu 1 at 35.928317s:

The buggy address belongs to the object at c00020003bda3000 which belongs to the cache kmalloc-rnd-15-2k of size 2048 The buggy address is located 16 bytes to the right of allocated 1448-byte region [c00020003bda3000, c00020003bda35a8)

The buggy address belongs to the physical page:

Memory state around the buggy address: c00020003bda3480: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 c00020003bda3500: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 >c00020003bda3580: 00 00 00 00 00 fc fc fc fc fc fc fc fc fc fc fc ^ c00020003bda3600: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc c00020003bda3680: fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc fc ==================================================================

Fix this by allocating the flexible array using nr_node_ids instead of num_possible_nodes(). Since nr_node_ids represents the maximum possible NUMA node IDs, indexing current_path[] using numa_node_id() becomes safe even on systems with sparse node IDs.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
59
EG Risk 59/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)
Severity98% × 45%
Impact severity (EG Severity): CVSS 9.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.5%
EPSS %ILE
43rd
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 (9.8): severity, escalated by confirmed exploitation. This CVE's 9.8 is its impact severity (EG Severity), not escalated.

EG Severity
9.8 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (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)3 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). 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

August 15, 2026

Last Modified

October 16, 2026

Advisory Details (8)

Auto-updated Oct 28, 2026
Patch available.
Web page

nvme-multipath: fix flex array size in struct nvme_ns_head - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme-multipath: fix flex array size in struct nvme_ns_head - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9ffdd11bd6c961b46b3689850ff6c5d7af5c5fe5
Web page

nvme-multipath: fix flex array size in struct nvme_ns_head - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e7b167e65610dfa7564d449474f4b477f9d4c1c
Web page

nvme-multipath: fix flex array size in struct nvme_ns_head - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7173a741fed73de6247384056fe92e582ba12507
Web page

nvme-multipath: fix flex array size in struct nvme_ns_head - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/316b5f1168264844aa125959de1d6da2b1905795
Web page

nvme-multipath: fix flex array size in struct nvme_ns_head - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1d4131b5c9823c7d2c86389898ad1b466af7df5e
Web page

nvme-multipath: fix flex array size in struct nvme_ns_head - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/140d6fff4ed266592492a23444043842b4af7a62
Web page

nvme-multipath: fix flex array size in struct nvme_ns_head - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/001e57554de81aa79c25c18fd53911d8a415c304

Vendor Advisories for CVE-2026-74384(1)

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

Patch Availability(15)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-34.34) @ resolute2026-11-01ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1014.14) @ resolute2026-11-01ubuntu
ubuntulinux-tools-nvidia-tegra-rt-6.8 (6.8.0-1035.38) @ noble2026-11-01ubuntu
ubuntulinux-tools-oracle-edge (7.0.0-1012.12~24.04.1) @ noble2026-11-01ubuntu
ubuntulinux-tools-gke-hwe-26.04 (7.0.0-1007.8) @ resolute2026-11-01ubuntu
ubuntulinux-tools-azure-fde-lts-22.04 (5.15.0.1122.131) @ jammy2026-11-01ubuntu
ubuntulinux-tools-gcp-edge (5.15.0.1118.128~20.04.1) @ focal2026-11-01ubuntu
ubuntulinux-tools-oracle-edge (5.15.0.1114.120~20.04.1) @ focal2026-11-01ubuntu
ubuntulinux-tools-gcp-lts-22.04 (5.15.0.1118.115) @ jammy2026-11-01ubuntu
ubuntulinux-xilinx-zynqmp-tools-5.15.0-1080 (5.15.0-1080.84) @ jammy2026-11-01ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1017.17) @ resolute2026-11-01ubuntu
ubuntulinux-tools-azure-fde-edge (7.0.0-1016.16~24.04.1) @ noble2026-11-01ubuntu
ubuntulinux-tools-nvidia-lowlatency-5.15 (5.15.0.1112.112) @ jammy2026-11-01ubuntu
ubuntulinux-virtual-6.8 (6.8.0-147.147) @ noble2026-11-01ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1071.79) @ noble2026-11-01ubuntu

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

(3 across 3 ecosystems)
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.1.106-1 ... 6.1.99-1 (55 versions)
  • every version up to 6.1.180-1: fixed in 6.1.180-1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.96-1 (31 versions)
  • every version up to 6.12.100-1: fixed in 6.12.100-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.1~rc7-1~exp1 (160 versions)
  • every version up to 7.1.5-1: fixed in 7.1.5-1
—

All Vendor Advisories

(15)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 25× in last 7d / 129× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 533 refreshes 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 433 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor)

Frequently asked(5)

What is CVE-2026-74384?
CVE-2026-74384 is a critical-severity vulnerability; its CVE record was published on August 15, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme-multipath: fix flex array size in struct nvme_ns_head struct nvme_ns_head contains a flexible array member, current_path[], which is indexed using the NUMA node ID: head->current_path[numa_node_id()] The structure is currently…
When was the CVE record for CVE-2026-74384 published?
The CVE record for CVE-2026-74384 was published on August 15, 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 16, 2026; the record at its source may have been updated since.
Is CVE-2026-74384 actively exploited?
CVE-2026-74384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (43rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-74384?
CVE-2026-74384 has a CVSS base score of 9.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-74384?
A fix for CVE-2026-74384 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-74384 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-74384

Explore →

Is Your Infrastructure Affected by CVE-2026-74384?

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

Book a Demo →Browse All CVEs