CVE-2026-23415

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-04-02. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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

futex: Fix UaF between futex_key_to_node_opt() and vma_replace_policy()

During futex_key_to_node_opt() execution, vma->vm_policy is read under speculative mmap lock and RCU. Concurrently, mbind() may call vma_replace_policy() which frees the old mempolicy immediately via kmem_cache_free().

This creates a race where __futex_key_to_node() dereferences a freed mempolicy pointer, causing a use-after-free read of mpol->mode.

[ 151.412631] BUG: KASAN: slab-use-after-free in __futex_key_to_node (kernel/futex/core.c:349) [ 151.414046] Read of size 2 at addr ffff888001c49634 by task e/87

[ 151.415969] Call Trace:

[ 151.416732] __asan_load2 (mm/kasan/generic.c:271) [ 151.416777] __futex_key_to_node (kernel/futex/core.c:349) [ 151.416822] get_futex_key (kernel/futex/core.c:374 kernel/futex/core.c:386 kernel/futex/core.c:593)

Fix by adding rcu to __mpol_put().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
40(Track)
EG Risk 40/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
KEV
Not listed

Published

April 2, 2026

Last Modified

August 5, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

futex: Fix UaF between futex_key_to_node_opt() and vma_replace_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/853f70c67d1b37e368fdcb3e328c4b8c04f53ac0
generic

futex: Fix UaF between futex_key_to_node_opt() and vma_replace_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/7e196194ea27bd49adf3551e2aceb83498eb73fe
generic

futex: Fix UaF between futex_key_to_node_opt() and vma_replace_policy() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/190a8c48ff623c3d67cb295b4536a660db2012aa

Vendor Advisories for CVE-2026-23415(2)

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

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:6.12.0-211.46.1.el10_22026-08-11redhat
redhatkernel-0:5.14.0-687.36.1.el9_82026-08-06redhat
linuxKernel @ 6.18.21osv

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

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 5× in last 7d / 27× 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 211 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-23415?
CVE-2026-23415 is a high vulnerability published on April 2, 2026. In the Linux kernel, the following vulnerability has been resolved: futex: Fix UaF between futexkeytonodeopt() and vmareplacepolicy() During futexkeytonodeopt() execution, vma->vm_policy is read under speculative mmap lock and RCU. Concurrently, mbind() may call vmareplacepolicy() which frees the…
When was CVE-2026-23415 disclosed?
CVE-2026-23415 was first published in the National Vulnerability Database on April 2, 2026, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23415 actively exploited?
CVE-2026-23415 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.9% of all scored CVEs.
What is the CVSS score of CVE-2026-23415?
CVE-2026-23415 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-23415?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23415, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-23415

Explore →

Is Your Infrastructure Affected by CVE-2026-23415?

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