Skip to content
Systems

CVE-2026-74541

8.8
High
EPSS 0.25%Patch availableAug 17, 2026

Linux kernel Bluetooth ISO use-after-free leading to kernel memory corruption.

common questions

Is CVE-2026-74541 being exploited?

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

How severe is CVE-2026-74541?

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

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

What does CVE-2026-74541 affect?

CVE-2026-74541 affects Linux kernel (Bluetooth ISO subsystem), Desktop Linux distros, Android devices using affected kernels, Embedded Linux/IoT devices with Bluetooth. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-74541?

Apply vendor/upstream kernel patches or updates immediately; disable Bluetooth if not required.

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)Desktop Linux distrosAndroid devices using affected kernelsEmbedded Linux/IoT devices with Bluetooth
impact

Bluetooth-triggered use-after-free can cause kernel crash, memory corruption and may allow privilege escalation or RCE via a remote/paired Bluetooth attacker.

action required

Patch when possible

affected versions
Linux Linux
  • affected>= fbdc4bc47268953c80853489f696e02d61f9a2c6 and < cc1d39946d62bc568551dfb81149724de1e91338
  • affected>= fbdc4bc47268953c80853489f696e02d61f9a2c6 and < 7b51a9c25e9698b64df9f2218f10eecf7dc7e2d0
  • affected>= fbdc4bc47268953c80853489f696e02d61f9a2c6 and < 63c0f396a18b767eb28e895eb95bbdce6c172c59
  • affected>= fbdc4bc47268953c80853489f696e02d61f9a2c6 and < 69a4a7b162b3db6ac337e3094cdee38f24d42ff7
  • affected>= fbdc4bc47268953c80853489f696e02d61f9a2c6 and < d57e506f6a1e3929611340fae87c1e4823f4d85c
  • affectedc03a10bd5b6ccb22921e04bcddc987410df7e7a9
  • affected>= 6.5.12 and < 6.6
  • affected6.6
vendor says fixed in< 6.6, >= 6.6.151 and <= 6.6.*, >= 6.12.103 and <= 6.12.*, >= 6.18.44 and <= 6.18.*, >= 7.1.8 and <= 7.1.*, >= 7.2 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