CVE-2026-74537
Use-after-free in Linux Bluetooth ISO allows kernel memory corruption and escalation.
Is CVE-2026-74537 being exploited?
Not confirmed. CVE-2026-74537 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-74537?
CVE-2026-74537 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-74537?
Yes. A fix has been recorded for CVE-2026-74537. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74537 affect?
CVE-2026-74537 affects Linux kernel (Bluetooth ISO subsystem), Linux distributions with affected kernels, Devices with Bluetooth ISO enabled (desktops, servers, embedded, IoT). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74537?
Apply vendor kernel updates promptly or disable Bluetooth until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
A proximate attacker via Bluetooth can trigger a use-after-free in the kernel ISO path to cause crashes or potentially achieve kernel code execution/privilege escalation.
Patch when possible
- affected>= 27c24fda62b601d6f9ca5e992502578c4310876f and < 4e9b5e8669b3602a4e01b6d1e9539b72e42c84d5
- affected>= 27c24fda62b601d6f9ca5e992502578c4310876f and < 1308d72903d792d10b82bc4ef08b8a4452308b04
- affected>= 27c24fda62b601d6f9ca5e992502578c4310876f and < 0d255e63fcf3f13a570d7ac11678fa1164ac015c
- affected5.15
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.