Skip to content
Systems

CVE-2026-63946

8.8
High
EPSS 0.34%Patch availableJul 21, 2026

Linux kernel Bluetooth ISO use-after-free causing kernel memory corruption.

common questions

Is CVE-2026-63946 being exploited?

Not confirmed. CVE-2026-63946 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.34% probability of exploitation in the next 30 days.

How severe is CVE-2026-63946?

CVE-2026-63946 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-63946?

Yes. A fix has been recorded for CVE-2026-63946. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-63946 affect?

CVE-2026-63946 affects Linux kernel (Bluetooth ISO subsystem), Linux distributions with affected kernels. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-63946?

Apply vendor kernel security updates or backported fix; disable Bluetooth if patch delayed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
Linux kernel (Bluetooth ISO subsystem)Linux distributions with affected kernels
impact

Nearby attacker can send crafted Bluetooth ISO frames to trigger a use-after-free, causing kernel crash or potential kernel RCE/privilege escalation.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= ccf74f2390d60a2f9a75ef496d2564abb478f46a and < c57ea90f203c8b8b41a474f19a09000d0f841436
  • affected>= ccf74f2390d60a2f9a75ef496d2564abb478f46a and < 119fb6f80c44dc1c65d604cf28e64c56bd9b6568
  • affected>= ccf74f2390d60a2f9a75ef496d2564abb478f46a and < b04ec131325baf4ea4577d6c6e6b86cf092e3731
  • affected>= ccf74f2390d60a2f9a75ef496d2564abb478f46a and < c318aa51830a3d2cc1229968fe521441c97356cd
  • affected>= ccf74f2390d60a2f9a75ef496d2564abb478f46a and < 1a6b803b00ccdd7666506adbe01ddae1c72d1ca9
  • affected>= ccf74f2390d60a2f9a75ef496d2564abb478f46a and < 47f23a259517abbdb8032c057a1e8a6bf3734878
  • affected6.0
vendor says fixed in< 6.0, >= 6.1.176 and <= 6.1.*, >= 6.6.143 and <= 6.6.*, >= 6.12.93 and <= 6.12.*, >= 6.18.35 and <= 6.18.*, >= 7.0.12 and <= 7.0.*, >= 7.1 and <= *

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free