CVE-2023-53024: bpf: Fix pointer-leak due to insufficient speculative store bypass mitigation
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.20% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 01bdcc73dbe7be3ad4d4ee9a59b71e42f461a528, 4.19.272, 5.10.166.
Low priority for now. Upgrade to Linux Linux 01bdcc73dbe7be3ad4d4ee9a59b71e42f461a528, 4.19.272, 5.10.166 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Mar 27, 2025
- Updated
- Nov 5, 2026
- EPSS
- 0.2% · 10th percentile
- CWE
- —
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 0b27bdf02c400684225ee5ee99970bcbf5082282, 5.14affected
- 872968502114d68c21419cf7eb5ab97717e7b803 and later · before aae109414a57ab4164218f36e2e4a17f027fcaaaaffected · git
- f5893af2704eb763eb982f01d573f5b19f06b623 and later · before 81b3374944d201872cfcf82730a7860f8e7c31ddaffected · git
- 0e9280654aa482088ee6ef3deadef331f5ac5fb0 and later · before da75dec7c6617bddad418159ffebcb133f008262affected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before 01bdcc73dbe7be3ad4d4ee9a59b71e42f461a528affected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before b0c89ef025562161242a7c19b213bd6b272e93dfaffected · git
- 2039f26f3aca5b0e419b98f65dd36481337b86ee and later · before e4f4db47794c9f474b184ee1418f42e6a07412b6affected · git
- 4.19.207 and later · before 4.19.272affected · semver
- 5.4.146 and later · before 5.4.231affected · semver
- 5.10.56 and later · before 5.10.166affected · semver
Affected versions · NVD (8)
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.19.207 and later · before 4.19.272
- linux linux kernel5.4.146 and later · before 5.4.231
- linux linux kernel5.10.56 and later · before 5.10.166
- linux linux kernel5.13.8 and later · before 5.14
- linux linux kernel5.14.1 and later · before 5.15.91
- linux linux kernel5.16 and later · before 6.1.9
- linux linux kernel5.14
- linux linux kernel6.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.11-1 | 6.1.11-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe…KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2023-53012Mar 27, 2025 · thermal: core: call put_device() only after device_register() fails22Monitor
- ← EarlierCVE-2023-53019Mar 27, 2025 · net: mdio: validate parameter addr in mdiobus_get_phy()31Monitor
- Later →CVE-2023-53031Mar 27, 2025 · powerpc/imc-pmu: Fix use of mutex in IRQs disabled section22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 01bdcc73dbe7be3ad4d4ee9a59b71e42f461a528 | Vendor (CNA) |
| Linux Linux | 4.19.272 | Vendor (CNA) |
| Linux Linux | 5.10.166 | Vendor (CNA) |
| Linux Linux | 5.14 | Vendor (CNA) |
| Linux Linux | 5.4.231 | Vendor (CNA) |
| Linux Linux | 81b3374944d201872cfcf82730a7860f8e7c31dd | Vendor (CNA) |
| Linux Linux | aae109414a57ab4164218f36e2e4a17f027fcaaa | Vendor (CNA) |
| Linux Linux | b0c89ef025562161242a7c19b213bd6b272e93df | Vendor (CNA) |
| Linux Linux | da75dec7c6617bddad418159ffebcb133f008262 | Vendor (CNA) |
| Linux Linux | e4f4db47794c9f474b184ee1418f42e6a07412b6 | Vendor (CNA) |
| debian:linux | 6.1.11-1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
—
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (2)
- SSVC exploitation— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/81b3374944d201872cfcf82730a7860f8e7c31dd
- git.kernel.org/stable/c/aae109414a57ab4164218f36e2e4a17f027fcaaa
- git.kernel.org/stable/c/b0c89ef025562161242a7c19b213bd6b272e93df
- git.kernel.org/stable/c/da75dec7c6617bddad418159ffebcb133f008262
- git.kernel.org/stable/c/e4f4db47794c9f474b184ee1418f42e6a07412b6
Vendor advisories and official records. Exploit/PoC links are deliberately left out.