Kernel compromise via misencoded BPF JIT branches
Published Jun 24, 2026 · Updated Jun 24, 2026
Incorrect branch encoding in the arm64 BPF JIT in Linux Kernel allows local users to gain kernel code execution via a crafted BPF program. The check_imm macro validates signed branch displacements against an N+1-bit range, after which aarch64_insn_encode_immediate masks an oversized value into the narrower field and can reverse branch direction. Reachability requires an arm64 kernel with BPF JIT enabled and permission to load a suitably large BPF program; invalid control flow can expose or write kernel memory, execute kernel code, or crash or hang the host.
Summary
What happened
Incorrect branch encoding in the arm64 BPF JIT in Linux Kernel allows local users to gain kernel code execution via a crafted BPF program. The check_imm macro validates signed branch displacements against an N+1-bit range, after which aarch64_insn_encode_immediate masks an oversized value into the narrower field and can reverse branch direction. Reachability requires an arm64 kernel with BPF JIT enabled and permission to load a suitably large BPF program; invalid control flow can expose or write kernel memory, execute kernel code, or crash or hang the host.
The record
- CVE
- CVE-2026-53036
- Published
- Jun 24, 2026
- Updated
- Jun 24, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-193, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2026CVE publishedPublication date reported by the CVE source.
- Jun 24, 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=3.18
- Affected versionversion=e54bcde3d69d40023ae77727213d14f920eb264a <1a113b5497297871699cd498b1b83542e0db7f15
- Affected versionversion=e54bcde3d69d40023ae77727213d14f920eb264a <1dd8be4ec722ce54e4cace59f3a4ba658111b3ec
- Affected versionversion=e54bcde3d69d40023ae77727213d14f920eb264a <6927f0d6794aa73318bbfa929f1ff6065b0620df
- Affected versionversion=e54bcde3d69d40023ae77727213d14f920eb264a <7fd3b41260c6120e7b60164afea5d961af6224f9
- Affected versionversion=e54bcde3d69d40023ae77727213d14f920eb264a <a5dfeb3b61065039488342d43ae06d4729d955d4
- Affected versionversion=e54bcde3d69d40023ae77727213d14f920eb264a <fb74defa1cca1a73177c0c761e641332e4f979a3
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.
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