CVE-2026-64508 is a Linux kernel BPF JIT hardening vulnerability related to Branch Target Reuse (BTR), a Spectre v2 variant. The BPF JIT allocator packs multiple small programs into shared executable allocations and reuses memory after programs are freed. Stale indirect-branch predictor entries from a prior program can remain associated with a reused address, causing an indirect branch into newly generated code to speculatively follow an obsolete target. This creates a transient execute-after-free-like speculative-control-flow primitive. The kernel fix adds an architecture-selectable indirect-branch-predictor flush before reused JIT memory is populated; the default implementation is a no-op unless an architecture enables a flush function.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
One of two CVEs assigned to the Branch Target Reuse (BTR) Spectre v2 variant. The attack reuses stale branch-target predictions following JIT code-memory reuse, allowing speculative data access that can be measured through cache side channels; researchers recovered a root password hash from a running Linux su process in minutes.
A Linux kernel CVE referenced as part of the mitigations released for the Branch Target Reuse Spectre-v2 variant.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.