CVE-2023-53024bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation
- 7.1HighCVSS base score
- 0.21%Exploitation in 30 daysEPSS · top 89% 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 pointer-leak due to insufficient speculative store bypass mitigation To mitigate Spectre v4, 2039f26f3aca ("bpf: Fix leakage due to insufficient speculative store bypass mitigation") inserts lfence instructions after 1) initializing a stack slot and 2) spilling a pointer to the stack. However, this does not cover cases where a stack slot is first initialized with a pointer (subject to sanitization) but then overwritten with a scalar (not subject to sanitization because the slot was already initialized). In this case, the second write may be subject to speculative store bypass (SSB) creating a speculative pointer-as-scalar type confusion. This allows the program to subsequently leak the numerical pointer value using, for example, a branch-based cache side channel. To fix this, also sanitize scalars if they write a stack slot that previously contained a pointer. Assuming that pointer-spills are only generated by LLVM on register-pressure, the performance impact on most real-world BPF programs should be small. The following unprivileged BPF bytecode drafts a minimal exploit and the mitigation: [...] // r6 = 0 or 1 (skalar, unknown user input) // r7 = accessible ptr for side channel // r10 = frame pointer (fp), to be leaked // r9 = r10 # fp alias to encourage ssb *(u64 *)(r9 - 8) = r10 // fp[-8] = ptr, to be leaked // lfence added here because of pointer spill to stack. // // Ommitted: Dummy bpf_ringbuf_output() here to train alias predictor // for no r9-r10 dependency. // *(u64 *)(r10 - 8) = r6 // fp[-8] = scalar, overwrites ptr // 2039f26f3aca: no lfence added because stack slot was not STACK_INVALID, // store may be subject to SSB // // fix: also add an lfence when the slot contained a ptr // r8 = *(u64 *)(r9 - 8) // r8 = architecturally a scalar, speculatively a ptr // // leak ptr using branch-based cache side channel: r8 &= 1 // choose bit to leak if r8 == 0 goto SLOW // no mispredict // architecturally dead code if input r6 is 0, // only executes speculatively iff ptr bit is 1 r8 = *(u64 *)(r7 + 0) # encode bit in cache (0: slow, 1: fast) SLOW: [...] After running this, the program can time the access to *(r7 + 0) to determine whether the chosen pointer bit was 0 or 1. Repeat this 64 times to recover the whole address on amd64. In summary, sanitization can only be skipped if one scalar is overwritten with another scalar. Scalar-confusion due to speculative store bypass can not lead to invalid accesses because the pointer bounds deducted during verification are enforced using branchless logic. See 979d63d50c0c ("bpf: prevent out of bounds speculation on pointer arithmetic") for details. Do not make the mitigation depend on !env->allow_{uninit_stack,ptr_leaks} because speculative leaks are likely unexpected if these were enabled. For example, leaking the address to a protected log file may be acceptable while disabling the mitigation might unintentionally leak the address into the cached-state of a map that is accessible to unprivileged processes.
Timeline
ID reserved
By Linux
Published
- 20 months later
· 20 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 | High7.1 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H |
- EPSS (exploitation in 30 days)
- 0.21% · top 89% 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: High 7.1.
Affected products
- affected 872968502114d68c21419cf7eb5ab97717e7b803 – < aae109414a57ab4164218f36e2e4a17f027fcaaa
- affected f5893af2704eb763eb982f01d573f5b19f06b623 – < 81b3374944d201872cfcf82730a7860f8e7c31dd
- affected 0e9280654aa482088ee6ef3deadef331f5ac5fb0 – < da75dec7c6617bddad418159ffebcb133f008262
- affected 2039f26f3aca5b0e419b98f65dd36481337b86ee – < 01bdcc73dbe7be3ad4d4ee9a59b71e42f461a528
- affected 2039f26f3aca5b0e419b98f65dd36481337b86ee – < b0c89ef025562161242a7c19b213bd6b272e93df
- affected 2039f26f3aca5b0e419b98f65dd36481337b86ee – < e4f4db47794c9f474b184ee1418f42e6a07412b6
- affected 0b27bdf02c400684225ee5ee99970bcbf5082282
- affected 4.19.207 – < 4.19.272
- affected 5.4.146 – < 5.4.231
- affected 5.10.56 – < 5.10.166
- affected 5.13.8 – < 5.14
- affected 5.14
- unaffected < 5.14
- unaffected 4.19.272 – ≤ 4.19.*
- unaffected 5.4.231 – ≤ 5.4.*
- unaffected 5.10.166 – ≤ 5.10.*
- unaffected 5.15.91 – ≤ 5.15.*
- unaffected 6.1.9 – ≤ 6.1.*
- unaffected 6.2 – ≤ *
References
References6
- https://git.kernel.org/stable/c/aae109414a57ab4164218f36e2e4a17f027fcaaa (opens in a new tab)
- https://git.kernel.org/stable/c/81b3374944d201872cfcf82730a7860f8e7c31dd (opens in a new tab)
- https://git.kernel.org/stable/c/da75dec7c6617bddad418159ffebcb133f008262 (opens in a new tab)
- https://git.kernel.org/stable/c/01bdcc73dbe7be3ad4d4ee9a59b71e42f461a528 (opens in a new tab)
- https://git.kernel.org/stable/c/b0c89ef025562161242a7c19b213bd6b272e93df (opens in a new tab)
- https://git.kernel.org/stable/c/e4f4db47794c9f474b184ee1418f42e6a07412b6 (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-2023-59696 (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-2023-53024)Record last updated .