CVE-2026-23244

HIGHNVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

Score 7.1 from GitHub Security Advisory (severity: HIGH) published 2026-03-18. NVD baseline CVSS 7.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 4 sources updated this week

Also known asEUVD-2026-12805 (ENISA EUVD) · GHSA-h4w6-67wq-xf89 (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

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

nvme: fix memory allocation in nvme_pr_read_keys()

nvme_pr_read_keys() takes num_keys from userspace and uses it to calculate the allocation size for rse via struct_size(). The upper limit is PR_KEYS_MAX (64K).

A malicious or buggy userspace can pass a large num_keys value that results in a 4MB allocation attempt at most, causing a warning in the page allocator when the order exceeds MAX_PAGE_ORDER.

To fix this, use kvzalloc() instead of kzalloc().

This bug has the same reasoning and fix with the patch below: https://lore.kernel.org/linux-block/20251212013510.3576091-1-kartikey406@gmail.com/

Warning log: WARNING: mm/page_alloc.c:5216 at __alloc_frozen_pages_noprof+0x5aa/0x2300 mm/page_alloc.c:5216, CPU#1: syz-executor117/272 Modules linked in: CPU: 1 UID: 0 PID: 272 Comm: syz-executor117 Not tainted 6.19.0 #1 PREEMPT(voluntary) Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org 04/01/2014 RIP: 0010:__alloc_frozen_pages_noprof+0x5aa/0x2300 mm/page_alloc.c:5216 Code: ff 83 bd a8 fe ff ff 0a 0f 86 69 fb ff ff 0f b6 1d f9 f9 c4 04 80 fb 01 0f 87 3b 76 30 ff 83 e3 01 75 09 c6 05 e4 f9 c4 04 01 <0f> 0b 48 c7 85 70 fe ff ff 00 00 00 00 e9 8f fd ff ff 31 c0 e9 0d RSP: 0018:ffffc90000fcf450 EFLAGS: 00010246 RAX: 0000000000000000 RBX: 0000000000000000 RCX: 1ffff920001f9ea0 RDX: 0000000000000000 RSI: 000000000000000b RDI: 0000000000040dc0 RBP: ffffc90000fcf648 R08: ffff88800b6c3380 R09: 0000000000000001 R10: ffffc90000fcf840 R11: ffff88807ffad280 R12: 0000000000000000 R13: 0000000000040dc0 R14: 0000000000000001 R15: ffffc90000fcf620 FS: 0000555565db33c0(0000) GS:ffff8880be26c000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: 000000002000000c CR3: 0000000003b72000 CR4: 00000000000006f0 Call Trace: alloc_pages_mpol+0x236/0x4d0 mm/mempolicy.c:2486 alloc_frozen_pages_noprof+0x149/0x180 mm/mempolicy.c:2557 ___kmalloc_large_node+0x10c/0x140 mm/slub.c:5598 __kmalloc_large_node_noprof+0x25/0xc0 mm/slub.c:5629 __do_kmalloc_node mm/slub.c:5645 [inline] __kmalloc_noprof+0x483/0x6f0 mm/slub.c:5669 kmalloc_noprof include/linux/slab.h:961 [inline] kzalloc_noprof include/linux/slab.h:1094 [inline] nvme_pr_read_keys+0x8f/0x4c0 drivers/nvme/host/pr.c:245 blkdev_pr_read_keys block/ioctl.c:456 [inline] blkdev_common_ioctl+0x1b71/0x29b0 block/ioctl.c:730 blkdev_ioctl+0x299/0x700 block/ioctl.c:786 vfs_ioctl fs/ioctl.c:51 [inline] __do_sys_ioctl fs/ioctl.c:597 [inline] __se_sys_ioctl fs/ioctl.c:583 [inline] __x64_sys_ioctl+0x1bf/0x220 fs/ioctl.c:583 x64_sys_call+0x1280/0x21b0 mnt/fuzznvme_1/fuzznvme/linux-build/v6.19/./arch/x86/include/generated/asm/syscalls_64.h:17 do_syscall_x64 arch/x86/entry/syscall_64.c:63 [inline] do_syscall_64+0x71/0x330 arch/x86/entry/syscall_64.c:94 entry_SYSCALL_64_after_hwframe+0x76/0x7e RIP: 0033:0x7fb893d3108d Code: 28 c3 e8 46 1e 00 00 66 0f 1f 44 00 00 f3 0f 1e fa 48 89 f8 48 89 f7 48 89 d6 48 89 ca 4d 89 c2 4d 89 c8 4c 8b 4c 24 08 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 c7 c1 b8 ff ff ff f7 d8 64 89 01 48 RSP: 002b:00007ffff61f2f38 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 RAX: ffffffffffffffda RBX: 00007ffff61f3138 RCX: 00007fb893d3108d RDX: 0000000020000040 RSI: 00000000c01070ce RDI: 0000000000000003 RBP: 0000000000000001 R08: 0000000000000000 R09: 00007ffff61f3138 R10: 0000000000000000 R11: 0000000000000246 R12: 0000000000000001 R13: 00007ffff61f3128 R14: 00007fb893dae530 R15: 0000000000000001

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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.1%
EPSS %ILE
2nd
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.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% 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; 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

March 18, 2026

Last Modified

June 17, 2026

Advisory Details (5)

Auto-updated Aug 2, 2026
Patch available.
Web page

nvme: fix memory allocation in nvme_pr_read_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: fix memory allocation in nvme_pr_read_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: fix memory allocation in nvme_pr_read_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: fix memory allocation in nvme_pr_read_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

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

nvme: fix memory allocation in nvme_pr_read_keys() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/15fb6d627484ee39ed73e202ef4720e1fa5c898e

Vendor Advisories for CVE-2026-23244(2)

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-6.8 (6.8.0-136.136) @ noble2026-10-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-10-25ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-10-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-10-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-10-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-10-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-10-25ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-10-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-10-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-10-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-10-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-10-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-10-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-10-25ubuntu
linuxKernel @ 6.6.130 (fixes >=6.5.0)—osv

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)
  • every version up to 6.12.85-1: fixed in 6.12.85-1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (121 versions)
  • every version up to 6.19.8-1: fixed in 6.19.8-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(14)

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 8× in last 7d / 44× 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 99 of 259 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 160 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-23244?
CVE-2026-23244 is a high-severity vulnerability; its CVE record was published on March 18, 2026. In the Linux kernel, the following vulnerability has been resolved: nvme: fix memory allocation in nvme_pr_read_keys() nvme_pr_read_keys() takes num_keys from userspace and uses it to calculate the allocation size for rse via struct_size(). The upper limit is PR_KEYS_MAX (64K). A malicious or buggy…
When was the CVE record for CVE-2026-23244 published?
The CVE record for CVE-2026-23244 was published on March 18, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-23244 actively exploited?
CVE-2026-23244 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-23244?
CVE-2026-23244 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-23244?
A fix for CVE-2026-23244 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-23244 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-23244

Explore →

Is Your Infrastructure Affected by CVE-2026-23244?

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

Book a Demo →Browse All CVEs