CVE-2026-74535
Linux kernel Bluetooth ISO timer bug causing deadlock and use-after-free
Is CVE-2026-74535 being exploited?
Not confirmed. CVE-2026-74535 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-74535?
CVE-2026-74535 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-74535?
Yes. A fix has been recorded for CVE-2026-74535. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74535 affect?
CVE-2026-74535 affects Linux kernel (Bluetooth ISO subsystem). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74535?
Apply upstream kernel Bluetooth patches and reboot affected hosts
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Nearby Bluetooth attacker can trigger kernel deadlock and a use-after-free, causing crashes or potential kernel-level code execution.
Patch when possible
- affected>= a58d0f5dac322e16cc75334d000666512341bde5 and < 16d89a63e08280abeef7218970a3bbd7ca62b021
- affected>= dc26097bdb864a0d5955b9a25e43376ffc1af99b and < 82e982f54f962f72646868ddbb2c3bd9ea178568
- affected>= dc26097bdb864a0d5955b9a25e43376ffc1af99b and < 3c3d5f85db80145636bb991a6005e2760012b985
- affected>= dc26097bdb864a0d5955b9a25e43376ffc1af99b and < 200fa1629c57a3ca2b03d3ca63fd3a9bfd910c43
- affectedf53e7489273dc2bb307bf50f319b3762d45534f0
- affected>= 6.12.2 and < 6.12.103
- affected>= 6.11.11 and < 6.12
- affected6.13
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.