CVE-2023-53024 Details
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.
A vulnerability in the Linux kernel's BPF (Berkeley Packet Filter) implementation allows for speculative leakage of pointer values, potentially leading to a type confusion exploit. This issue arises from inadequate mitigation of Spectre variant 4, where stack slots initialized with pointers can be overwritten by scalars, creating a speculative pointer-as-scalar confusion. The vulnerability can be exploited to leak pointer values through a branch-based cache side channel.
The vulnerability has been addressed by updating the BPF mitigation to also sanitize scalar writes that overwrite stack slots previously containing pointers, ensuring that speculative store bypass attacks cannot be used to leak pointer values.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Nov 5, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/01bdcc73dbe7be3ad4d4ee9a59b71e42f461a528 | kernel.org | Patch |
| https://git.kernel.org/stable/c/81b3374944d201872cfcf82730a7860f8e7c31dd | kernel.org | Patch |
| https://git.kernel.org/stable/c/aae109414a57ab4164218f36e2e4a17f027fcaaa | kernel.org | Patch |
| https://git.kernel.org/stable/c/b0c89ef025562161242a7c19b213bd6b272e93df | kernel.org | Patch |
| https://git.kernel.org/stable/c/da75dec7c6617bddad418159ffebcb133f008262 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e4f4db47794c9f474b184ee1418f42e6a07412b6 | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 4.19.207, < 4.19.272 >= 5.4.146, < 5.4.231 >= 5.10.56, < 5.10.166 >= 5.13.8, < 5.14 >= 5.14.1, < 5.15.91 >= 5.16, < 6.1.9 5.14 - 5.14 rc4 5.14 rc5 5.14 rc6 5.14 rc7 6.2 rc1 6.2 rc2 6.2 rc3 6.2 rc4 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Nov 5, 2026 | CVE Modified | kernel.org |
| Nov 5, 2026 | CVE Modified | CISA-ADP |
| Jun 17, 2026 | CVE Modified | kernel.org |
| Jan 22, 2026 | Initial Analysis | [email protected] |
| Mar 27, 2025 | New CVE Received | kernel.org |