CVE-2026-46138
Linux kernel Bluetooth: OOB read causes infinite loop in BIG setup.
Is CVE-2026-46138 being exploited?
Not confirmed. CVE-2026-46138 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.28% probability of exploitation in the next 30 days.
How severe is CVE-2026-46138?
CVE-2026-46138 is rated High with a CVSS score of 8.1. 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-46138?
Yes. A fix has been recorded for CVE-2026-46138. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-46138 affect?
CVE-2026-46138 affects Linux kernel, Bluetooth stack (HCI). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-46138?
Update to patched kernel version.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Possible DoS: malformed LE_Create_BIG_Complete loops indefinitely in BT BIG setup, system hangs.
Patch when possible
- affected>= a0bfde167b506423111ddb8cd71930497a40fc54 and < 6cb7f67bc28da787499291a562d49a084d9c90cd
- affected>= a0bfde167b506423111ddb8cd71930497a40fc54 and < 22559ad7654f61727fc270ee4893da9f4b70cf17
- affected>= a0bfde167b506423111ddb8cd71930497a40fc54 and < 77981a507aa0fc001dc37f0dd6631dd2042fed17
- affected>= a0bfde167b506423111ddb8cd71930497a40fc54 and < 665da0baaf0396f9ed3c86ccb3955dcd0b73e774
- affected>= a0bfde167b506423111ddb8cd71930497a40fc54 and < 5ddb8014261137cadaf83ab5617a588d80a22586
- affectedb475c1109251e30ec21fb574d72a1c71a4ab0039
- affected2ccde10127447c1a5caad8469fede945bdb62fdf
- affected>= 6.4.16 and < 6.5
- affected>= 6.5.3 and < 6.6
- affected6.6
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.