{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-64507 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-64507 is a vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-64507 and fix it if it is affected.\n\nWhat it is: CVE-2026-64507 is a vulnerability in Linux, published on 25 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-64507 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-64507/ (Markdown: https://insights.sbomify.com/CVE-2026-64507/index.md)","id":"CVE-2026-64507","markdown":"https://insights.sbomify.com/CVE-2026-64507/index.md","name":"CVE-2026-64507","record":{"aliases":["AZL-93809","BELL-CVE-2026-64507","DEBIAN-CVE-2026-64507","GHSA-mfjh-rff8-525v","ROOT-OS-UBUNTU-2204-CVE-2026-64507","UBUNTU-CVE-2026-64507"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"Linux kernel","requires_auth":"low_privilege","summary":"Attackers can bypass Spectre-v2 mitigations via BPF JIT memory reuse, requiring local access and specific kernel configurations.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nx86/bugs: Enable IBPB flush on BPF JIT allocation\n\nEnable hardening against JIT spraying when Spectre-v2 mitigations are in\nuse. Specifically, issue an IBPB flush on BPF JIT memory reuse. Skip\nenabling the IBPB flush if the BPF dispatcher is already using a retpoline\nsequence.\n\nThis hardening applies only when BPF-JIT is in use. Guard the enabling\nunder CONFIG_BPF_JIT so that bugs.c still builds with CONFIG_BPF_JIT=n.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-10-15","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-10-15T22:48:12Z","kind":"github_poc","ref":"https://github.com/manalejandro/CVE-2026-64507","stars":0,"title":"CVE-2026-64507 — PoC: IBPB flush on BPF JIT allocation"}],"tier":"poc_unverified"},"has_fix":true,"headline":"x86/bugs: Enable IBPB flush on BPF JIT allocation","id":"CVE-2026-64507","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"bpf: Support for hardening against JIT spraying","id":"CVE-2026-64508"},"packages":[],"prev":{"headline":"wifi: rtw89: correct drop logic for malformed AMPDU frames","id":"CVE-2026-64506"},"products":["Linux"],"published":"2026-07-25","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-08-19","vendors":["Linux"]},"summary":"Attackers can bypass Spectre-v2 mitigations via BPF JIT memory reuse, requiring local access and specific kernel configurations.","url":"https://insights.sbomify.com/CVE-2026-64507/"}