CVE-2026-63975
Bluetooth L2CAP flaw can crash Linux kernel remotely (DoS).
Is CVE-2026-63975 being exploited?
Not confirmed. CVE-2026-63975 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.35% probability of exploitation in the next 30 days.
How severe is CVE-2026-63975?
CVE-2026-63975 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-63975?
Yes. A fix has been recorded for CVE-2026-63975. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-63975 affect?
CVE-2026-63975 affects Linux kernel (Bluetooth L2CAP subsystem), Linux-based devices with Bluetooth (servers, desktops, embedded, Android kernels). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-63975?
Apply vendor/kernel updates; disable Bluetooth if immediate patching isn't possible.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote kernel crash via crafted Bluetooth L2CAP packets causing denial-of-service and device instability.
Patch when possible
- affected>= 15f02b91056253e8cdc592888f431da0731337b8 and < 3c8eaa91eb433c450426539290be4ffe282e9f00
- affected>= 15f02b91056253e8cdc592888f431da0731337b8 and < ecfed1e0d8efecad6737a0d83e21d2fd021d8c48
- affected>= 15f02b91056253e8cdc592888f431da0731337b8 and < e6833e737a51db1e5ea0401322acf5e22abd8be6
- affected>= 15f02b91056253e8cdc592888f431da0731337b8 and < 6319b38fe69f56ed95680ade485b957a53fff642
- affected>= 15f02b91056253e8cdc592888f431da0731337b8 and < 291eec1041c918c460dc9702e44edd17794b4a4b
- affected>= 15f02b91056253e8cdc592888f431da0731337b8 and < 41e29548b5e8b5e5fcf708786b3bea67cab107fa
- affected>= 15f02b91056253e8cdc592888f431da0731337b8 and < d153b8898c0051eb8b6a083b35cbe304a5886bd5
- affected>= 15f02b91056253e8cdc592888f431da0731337b8 and < 41c2713b204e6cb6a94587bc6bf6935107df5479
- affected5.7
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.