CVE-2026-74300
Linux kernel Bluetooth HCI length validation flaw causes kernel memory corruption.
Is CVE-2026-74300 being exploited?
Not confirmed. CVE-2026-74300 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.26% probability of exploitation in the next 30 days.
How severe is CVE-2026-74300?
CVE-2026-74300 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-74300?
Yes. A fix has been recorded for CVE-2026-74300. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-74300 affect?
CVE-2026-74300 affects Linux kernel (hci_read_codec_capabilities), Linux distributions with affected kernels, Devices with Linux Bluetooth (Android/embedded). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-74300?
Apply kernel/vendor patches and Bluetooth firmware updates; limit Bluetooth access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Kernel memory corruption from malformed Bluetooth controller response, enabling crashes, possible info disclosure, or local/nearby privilege escalation/code execution.
Patch when possible
- affected>= 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and < fc97fc8cf7f53fd3619db63e09050d20a3a0c4b1
- affected>= 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and < 290b36f9d1eb9b2f72b40d826f26b4a182ab15f7
- affected>= 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and < f2ad01f55e07f9531efcea736087e6b8658a3440
- affected>= 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and < ec4d352747a62c1082f16c11a74b37d6eb85a5a3
- affected>= 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and < 4bc16db0f11918e07edf9fdcda4a30cf4c9df45c
- affected>= 8961987f3f5fa2f2618e72304d013c8dd5e604a6 and < c38fbcdc407925c7088f7e5f11c1fff73d2d35a2
- affected5.16
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.