Skip to content
Noroxi
NVD / CVE Program· CNA Linux

CVE-2026-64508: bpf: Support for hardening against JIT spraying

Noroxi assessment

Priority: Monitor (action score 0/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.18% (FIRST EPSS).
  • Fixed version: Linux Linux 1fbafd5235ca897b322161659ebe8ba651b00b3b, 6e52c240c43a601b681e3a4e58fc5685114d4726, 7a6c171c6a1ac6d1509752dac131d941a3de0b37; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1.

Low priority for now. Upgrade to Linux Linux 1fbafd5235ca897b322161659ebe8ba651b00b3b, 6e52c240c43a601b681e3a4e58fc5685114d4726, 7a6c171c6a1ac6d1509752dac131d941a3de0b37; azl3 kernel 6.6.144.1-1 on Azure Linux 3.0 6.6.145.2-1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

In the Linux kernel, the following vulnerability has been resolved: bpf: Support for hardening against JIT spraying The BPF JIT allocator packs many small programs into larger executable allocations and reuses space within those allocations as programs are loaded and freed. When fresh code is written into space that a previous program occupied, an indirect jump into the new program can reuse a branch prediction left behind by the old one. Flush the indirect branch predictors before reusing JIT memory so that indirect jumps into a newly written program don't reuse predictions from an old program that occupied the same space. Introduce bpf_arch_pred_flush_enabled static key and bpf_arch_pred_flush static call for flushing the branch predictors on JIT memory reuse. Architectures that need a flush, can update it to a predictor flush function. By default, its a NOP and does not emit any CALL. Allocations larger than a pack are not covered by this flush. That is safe because cBPF programs (the unprivileged attack surface) are bounded well below a pack size. Issue a warning if this assumption is ever violated while the flush is active.

—No exploit Fix available
Published
Jul 25, 2026
Updated
Aug 19, 2026
EPSS
0.1% · 8th percentile
CWE
—

Report tools

JSON

Action score

0

Monitor

Low priority for now.

CVSS
0 / 40 · —
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64508

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.

  • Linux Linux

    • 5.18affected
    • 57631054fae6dcc9c892ae6310b58bbb6f6e5048 and later · before 1fbafd5235ca897b322161659ebe8ba651b00b3baffected · git
    • 57631054fae6dcc9c892ae6310b58bbb6f6e5048 and later · before 6e52c240c43a601b681e3a4e58fc5685114d4726affected · git
    • 57631054fae6dcc9c892ae6310b58bbb6f6e5048 and later · before eed774da601268dae674e14d54a15e3624691f52affected · git
    • 57631054fae6dcc9c892ae6310b58bbb6f6e5048 and later · before 8ff183ee4d8c452960df58175a094828c0513b2eaffected · git
    • 57631054fae6dcc9c892ae6310b58bbb6f6e5048 and later · before 7a6c171c6a1ac6d1509752dac131d941a3de0b37affected · git
    • 57631054fae6dcc9c892ae6310b58bbb6f6e5048 and later · before 96cce16e26dd02a8678f1e87f88a4b5cdb63b995affected · git
    • before 5.18not affected · semver
    • 6.1.183 and later · up to and including 6.1.*not affected · semver
    • 6.6.145 and later · up to and including 6.6.*not affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
AlmaLinux:10kernelbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64kbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debugbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-debug-modules-extrabefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-64k-modules-extrabefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-abi-stablelistsbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-cross-headersbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debugbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-develbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-devel-matchedbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-modulesbefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2
AlmaLinux:10kernel-debug-modules-corebefore 6.12.0-211.65.1.el10_26.12.0-211.65.1.el10_2

+96

Other highest-scoring records for the same primary product.

  • CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation
    40Plan
  • CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment
    40Plan
  • CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-64506Jul 25, 2026 · wifi: rtw89: correct drop logic for malformed AMPDU frames
    0Monitor
  • ← EarlierCVE-2026-64507Jul 25, 2026 · x86/bugs: Enable IBPB flush on BPF JIT allocation
    0Monitor
  • Later →CVE-2026-64509Jul 25, 2026 · rust: block: fix GenDisk cleanup paths
    0Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Linux Linux1fbafd5235ca897b322161659ebe8ba651b00b3bVendor (CNA)
Linux Linux6e52c240c43a601b681e3a4e58fc5685114d4726Vendor (CNA)
Linux Linux7a6c171c6a1ac6d1509752dac131d941a3de0b37Vendor (CNA)
Linux Linux8ff183ee4d8c452960df58175a094828c0513b2eVendor (CNA)
Linux Linux96cce16e26dd02a8678f1e87f88a4b5cdb63b995Vendor (CNA)
Linux Linuxeed774da601268dae674e14d54a15e3624691f52Vendor (CNA)
azl3 kernel 6.6.144.1-1 on Azure Linux 3.06.6.145.2-1 · CBL-Mariner ReleasesMicrosoft (MSRC)
almalinux:kernel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-devel-matched6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-core6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-debug-modules-extra6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
almalinux:kernel-64k-devel-matched6.12.0-211.65.1.el10_2 · AlmaLinux:10Package registry (OSV)
debian:linux6.1.187-1 · Debian:12Package registry (OSV)
debian:linux-6.126.12.100-1~deb12u1 · Debian:12Package registry (OSV)
red hat:kernel-64k-debug-debuginfo0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debug-devel-matched0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-debuginfo0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-64k-devel-matched0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-debuginfo0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)
red hat:kernel-debug-devel-matched0:6.12.0-211.65.1.el10_2 · Red Hat:enterprise_linux:10.2Package registry (OSV)

+4

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

No CVSS vector for this record, so attack conditions can't be derived.

Weakness class (CWE)

—

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records