Kernel crash via uninitialized BPF frame pointer
Published Aug 19, 2025 · Updated Aug 5, 2026
Kernel memory corruption in the ARM64 BPF JIT in Linux allows local users to crash the kernel through a crafted BPF program. Exception-boundary programs bypass find_used_callee_regs(), leaving ctx->fp_used false even when the frame pointer is used, so the prologue does not initialize it. Loading the trigger requires CAP_BPF, and execution can dereference the uninitialized pointer and page-fault the kernel.
Summary
What happened
Kernel memory corruption in the ARM64 BPF JIT in Linux allows local users to crash the kernel through a crafted BPF program. Exception-boundary programs bypass find_used_callee_regs(), leaving ctx->fp_used false even when the frame pointer is used, so the prologue does not initialize it. Loading the trigger requires CAP_BPF, and execution can dereference the uninitialized pointer and page-fault the kernel.
The record
- CVE
- CVE-2025-38586
- Published
- Aug 19, 2025
- Updated
- Aug 5, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- admin
Timeline
How it unfolded
- Aug 19, 2025CVE publishedPublication date reported by the CVE source.
- Aug 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff <0dbef493cae7d451f740558665893c000adb2321
- Affected versionversion=5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff <1ce30231e0a2c8c361ee5f8f7f265fc17130adce
- Affected versionversion=5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff <b114fcee766d5101eada1aca7bb5fd0a86c89b35
- Affected versionversion=5d4fa9ec5643a5c75d3c1e6abf50fb9284caf1ff <e23184725dbb72d5d02940222eee36dbba2aa422
- Affected versionversion=6.12
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo