Bluetooth: 6lowpan: check skb_clone() return value in send_mcast_pkt()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 18722c247023035b9e2e2a08a887adec2a9a6e49 · < e673889a35a5e4c586d0fae67d8755ca4367d3e2| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: 6lowpan: check skb_clone() return value in send_mcast_pkt()
The skb_clone() function can return NULL if memory allocation fails. send_mcast_pkt() calls skb_clone() without checking the return value, which can lead to a NULL pointer dereference in send_pkt() when it dereferences skb->data. Add a NULL check after skb_clone() and skip the peer if the clone fails.
From the CVE record · Linux
The Linux kernel's Bluetooth 6lowpan multicast send path does not check whether skb_clone() fails when memory allocation fails. This can cause a NULL pointer dereference in send_pkt(). The input does not establish whether an attacker can trigger the failure or what access would be required.
Teams running Linux kernels with the affected Bluetooth 6lowpan code should check their kernel version; affected versions are not specified.