Bluetooth: ISO: fix malformed ISO_END/CONT handling
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ ccf74f2390d60a2f9a75ef496d2564abb478f46a · < e054c1a6ae7310d2815778fddb87da616e11c255| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: ISO: fix malformed ISO_END/CONT handling
Core specification (Part C vol 4 sec 5.4.5) does not exclude empty ISO_CONT, ISO_END packets. We currently reject them if they are last.
If controller sends malformed sequence
ISO_START -> rx_len = 4, ISO_CONT skb->len 4, ISO_START
that ends payload in ISO_CONT, we leak conn->rx_skb. If controller sends too long ISO_END, we panic on skb_put. If controller sends too short ISO_END we accept it.
Fix by marking unfinished ISO_START via conn->rx_skb != NULL. Check skb->len properly before skb_put. Combine the ISO_CONT/END code paths as they require the same initial checks. Reject too short ISO_END packets.
From the CVE record · Linux
The Linux kernel mishandles malformed Bluetooth ISO_CONT and ISO_END packet sequences. If a controller sends these packets, an overly long ISO_END can cause a kernel panic, while another malformed sequence can leak receive-buffer memory; the input does not establish whether authentication or user interaction is required.
Engineers running Linux kernels with Bluetooth ISO support should check their deployments; affected versions were not provided.