Kernel control-flow hijack via torn BPF target
Published Mar 25, 2026 · Updated Mar 25, 2026
Atomic tearing in the arm64 BPF JIT in Linux Kernel allows local users to hijack kernel control flow through BPF program activity. The bpf_jit_binary_pack_alloc() function gives the JIT buffer only 4-byte alignment, so build_plt() can place the u64 bpf_plt.target field off an 8-byte boundary while bpf_arch_text_poke() updates it and JIT code loads it. The path requires local access and delegated BPF capabilities; a torn target can redirect kernel execution, expose or alter kernel memory, or panic the system.
Summary
What happened
Atomic tearing in the arm64 BPF JIT in Linux Kernel allows local users to hijack kernel control flow through BPF program activity. The bpf_jit_binary_pack_alloc() function gives the JIT buffer only 4-byte alignment, so build_plt() can place the u64 bpf_plt.target field off an 8-byte boundary while bpf_arch_text_poke() updates it and JIT code loads it. The path requires local access and delegated BPF capabilities; a torn target can redirect kernel execution, expose or alter kernel memory, or panic the system.
The record
- CVE
- CVE-2026-23383
- Published
- Mar 25, 2026
- Updated
- Mar 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 25, 2026CVE publishedPublication date reported by the CVE source.
- Mar 25, 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=6.0
- Affected versionversion=b2ad54e1533e91449cb2a371e034942bd7882b58 <519b1ad91de5bf7a496f2b858e9212db6328e1de
- Affected versionversion=b2ad54e1533e91449cb2a371e034942bd7882b58 <66959ed481a474eaae278c7f6860a2a9b188a4d6
- Affected versionversion=b2ad54e1533e91449cb2a371e034942bd7882b58 <80ad264da02cc4aee718e799c2b79f0f834673dc
- Affected versionversion=b2ad54e1533e91449cb2a371e034942bd7882b58 <ef06fd16d48704eac868441d98d4ef083d8f3d07
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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