Bluetooth: L2CAP: validate frame length before control and FCS access
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1c2acffb76d4bc5fd27c4ea55cc27ad8ead10f9a · < c6a288e6001bcce16553c3853e0f5a45eaaf85c7| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: validate frame length before control and FCS access
l2cap_data_rcv() unpacks either a two-byte or four-byte control field without first ensuring that it is present. A short ERTM or streaming-mode frame can therefore cause an out-of-bounds read.
There is a second short-frame case when CRC16 is enabled. After the control field is pulled, l2cap_check_fcs() subtracts two from skb->len without checking it. If fewer than two bytes remain, the subtraction wraps; skb_trim() leaves the buffer unchanged and the subsequent FCS load reads past the logical end of the frame.
Validate that the frame contains both its control field and, when enabled, its FCS before either field is accessed.
From the CVE record · Linux
The Linux kernel's Bluetooth L2CAP receiver does not check that a short ERTM or streaming-mode frame contains its control field before reading it. A short frame can cause an out-of-bounds read; when CRC16 is enabled, a frame with fewer than two bytes remaining after the control field can also cause a read past the frame's logical end. The input does not specify attacker access requirements or whether user interaction is needed.
Engineers running the Linux kernel with Bluetooth L2CAP should check their installations; affected versions are not specified.