JIT spraying via reused branch predictions
Published Jul 25, 2026 · Updated Jul 25, 2026
JIT spraying in the Linux kernel BPF JIT allows local users to reuse stale branch predictions when executable memory is recycled. The BPF JIT allocator rewrites freed slots inside shared executable packs without first flushing indirect branch predictors, so new code inherits predictions trained by the program that previously occupied the slot. Unprivileged cBPF programs form the exposed path; the vendor has not published a concrete confidentiality, integrity, or availability consequence beyond the JIT-spraying primitive.
Summary
What happened
JIT spraying in the Linux kernel BPF JIT allows local users to reuse stale branch predictions when executable memory is recycled. The BPF JIT allocator rewrites freed slots inside shared executable packs without first flushing indirect branch predictors, so new code inherits predictions trained by the program that previously occupied the slot. Unprivileged cBPF programs form the exposed path; the vendor has not published a concrete confidentiality, integrity, or availability consequence beyond the JIT-spraying primitive.
The record
- CVE
- CVE-2026-64508
- Published
- Jul 25, 2026
- Updated
- Jul 25, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- Unavailable
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 25, 2026CVE publishedPublication date reported by the CVE source.
- Jul 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=0 <6.12.97
- Affected versionversion=0 <6.18.39
- Affected versionversion=0 <6.6.145
- Affected versionversion=0 <7.1.4
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6e52c240c43a601b681e3a4e58fc5685114d4726
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <7a6c171c6a1ac6d1509752dac131d941a3de0b37
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <8ff183ee4d8c452960df58175a094828c0513b2e
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <96cce16e26dd02a8678f1e87f88a4b5cdb63b995
- Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <eed774da601268dae674e14d54a15e3624691f52
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
No sourced classifications are available.
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