CVE-2026-23417bpf: Fix constant blinding for PROBE_MEM32 stores
- 5.5MediumCVSS base score
- 0.12%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
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.
Timeline
ID reserved
By Linux
- 3 months later
· 3 months later
Published
- 7 months later
· 7 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| NVDNVD · Analyzed | 3.1 | Medium5.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.12% · top 98% of all CVEs (19 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: partial
The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.
Affected products
- affected 6082b6c328b5486da2b356eae94b8b83c98b5565 – < 56af722756ed82fee2ae5d5b4d04743407506195
- affected 6082b6c328b5486da2b356eae94b8b83c98b5565 – < ccbf29b28b5554f9d65b2fb53b994673ad58b3bf
- affected 6082b6c328b5486da2b356eae94b8b83c98b5565 – < de641ea08f8fff6906e169d2576c2ac54e562fbb
- affected 6082b6c328b5486da2b356eae94b8b83c98b5565 – < 2321a9596d2260310267622e0ad8fbfa6f95378f
- affected 6.9
- unaffected < 6.9
- unaffected 6.12.80 – ≤ 6.12.*
- unaffected 6.18.21 – ≤ 6.18.*
- unaffected 6.19.11 – ≤ 6.19.*
- unaffected 7.0 – ≤ *
References
References4
- https://git.kernel.org/stable/c/56af722756ed82fee2ae5d5b4d04743407506195 (opens in a new tab)
- https://git.kernel.org/stable/c/ccbf29b28b5554f9d65b2fb53b994673ad58b3bf (opens in a new tab)
- https://git.kernel.org/stable/c/de641ea08f8fff6906e169d2576c2ac54e562fbb (opens in a new tab)
- https://git.kernel.org/stable/c/2321a9596d2260310267622e0ad8fbfa6f95378f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-18200 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-23417)Record last updated .