Bluetooth: ISO: drop ISO_END frames received without prior ISO_START
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ccf74f2390d60a2f9a75ef496d2564abb478f46a · < 84c24fb151fc1179355296d7ff29129ac7c42129| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: ISO: drop ISO_END frames received without prior ISO_START
ISO data PDUs carry a packet-boundary flag indicating START, CONT, END or SINGLE. The ISO_CONT branch of iso_recv() guards against a missing ISO_START by checking conn->rx_len before touching conn->rx_skb, but ISO_END does not.
If a peer sends an ISO_END as the first packet on a fresh ISO connection, conn->rx_skb is still NULL and conn->rx_len is zero, so skb_put(conn->rx_skb, ...) dereferences NULL and oopses. For BIS, where receivers sync to a broadcaster without pairing, any broadcaster on the air can trigger this.
Mirror the ISO_CONT check at the top of ISO_END so a stray end fragment is logged and dropped instead of crashing the host.
From the CVE record · Linux
The Linux kernel’s Bluetooth ISO receive path can dereference a NULL pointer if an ISO_END frame arrives before ISO_START, crashing the host. A peer can trigger this on a fresh ISO connection; for BIS, an on-air broadcaster can do so without pairing.
Operators of Linux systems using Bluetooth ISO should check their kernel; affected versions were not specified.