Affects the Linux kernel (widely deployed). Exploitation can crash hosts or enable local privilege escalation, impacting servers, cloud hosts, and endpoints.
CVE-2026-63865
Linux kernel BPF LSM hooks called in atomic contexts can cause kernel panic/DoS.
Is CVE-2026-63865 being exploited?
Not confirmed. CVE-2026-63865 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.13% probability of exploitation in the next 30 days.
How severe is CVE-2026-63865?
CVE-2026-63865 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-63865?
Yes. A fix has been recorded for CVE-2026-63865. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63865 affect?
CVE-2026-63865 affects Linux kernel (BPF LSM), Linux distributions with BPF LSM enabled. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63865?
Install vendor kernel updates and restrict/unload untrusted BPF LSM modules.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Local attacker or malicious BPF LSM can sleep in atomic context causing kernel panic/DoS and potential privilege escalation.
Patch when possible
- affected>= 423f16108c9d832bd96059d5c882c8ef6d76eb96 and < 452a927cddcd67478d030e646f41cb904a93156f
- affected>= 423f16108c9d832bd96059d5c882c8ef6d76eb96 and < f0fc2a9828171205244a28013f02889f50b71c9f
- affected>= 423f16108c9d832bd96059d5c882c8ef6d76eb96 and < 26b380a3ca0b605fd8860995ed6a208f276dd316
- affected>= 423f16108c9d832bd96059d5c882c8ef6d76eb96 and < 0d918263c9bfc86078edb2e2f7302a0c6ce42b7c
- affected>= 423f16108c9d832bd96059d5c882c8ef6d76eb96 and < 281f2a214565a5cbf8b7355a65738d80bd19b8c5
- affected>= 423f16108c9d832bd96059d5c882c8ef6d76eb96 and < 989f1b93907de1753a814996222da375f07e579b
- affected>= 423f16108c9d832bd96059d5c882c8ef6d76eb96 and < beaf0e96b1da74549a6cabd040f9667d83b2e97e
- affected5.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.