CVE-2026-23417

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-04-02. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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

bpf: Fix constant blinding for PROBE_MEM32 stores

BPF_ST | BPF_PROBE_MEM32 immediate stores are not handled by bpf_jit_blind_insn(), allowing user-controlled 32-bit immediates to survive unblinded into JIT-compiled native code when bpf_jit_harden >= 1.

The root cause is that convert_ctx_accesses() rewrites BPF_ST|BPF_MEM to BPF_ST|BPF_PROBE_MEM32 for arena pointer stores during verification, before bpf_jit_blind_constants() runs during JIT compilation. The blinding switch only matches BPF_ST|BPF_MEM (mode 0x60), not BPF_ST|BPF_PROBE_MEM32 (mode 0xa0). The instruction falls through unblinded.

Add BPF_ST|BPF_PROBE_MEM32 cases to bpf_jit_blind_insn() alongside the existing BPF_ST|BPF_MEM cases. The blinding transformation is identical: load the blinded immediate into BPF_REG_AX via mov+xor, then convert the immediate store to a register store (BPF_STX).

The rewritten STX instruction must preserve the BPF_PROBE_MEM32 mode so the architecture JIT emits the correct arena addressing (R12-based on x86-64). Cannot use the BPF_STX_MEM() macro here because it hardcodes BPF_MEM mode; construct the instruction directly instead.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

April 2, 2026

Last Modified

April 24, 2026

Advisory Details (4)

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

bpf: Fix constant blinding for PROBE_MEM32 stores - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix constant blinding for PROBE_MEM32 stores - kernel/git/stable/linux.git - Linux kernel stable tree

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

bpf: Fix constant blinding for PROBE_MEM32 stores - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/56af722756ed82fee2ae5d5b4d04743407506195
generic

bpf: Fix constant blinding for PROBE_MEM32 stores - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/2321a9596d2260310267622e0ad8fbfa6f95378f

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
linuxKernel @ 6.12.80—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 rangeFixed inDependents
linux6.12.38-1 ... 6.12.85-1~bpo12+1 (17 versions)6.12.85-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.19~rc8-1~exp1 (124 versions)6.19.11-1—

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-23417?
CVE-2026-23417 is a medium vulnerability published on April 2, 2026. In the Linux kernel, the following vulnerability has been resolved: bpf: Fix constant blinding for PROBE_MEM32 stores BPFST | BPFPROBE_MEM32 immediate stores are not handled by bpfjitblind_insn(), allowing user-controlled 32-bit immediates to survive unblinded into JIT-compiled native code when…
When was CVE-2026-23417 disclosed?
CVE-2026-23417 was first published in the National Vulnerability Database on April 2, 2026, with the most recent update on April 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23417 actively exploited?
CVE-2026-23417 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 98.2% of all scored CVEs.
What is the CVSS score of CVE-2026-23417?
CVE-2026-23417 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-23417?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23417, 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-23417

Explore →

Is Your Infrastructure Affected by CVE-2026-23417?

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

Start Free Scan →Browse All CVEs