Bluetooth: purge error queues in socket destructors
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
6.18.176.19.77.0In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: purge error queues in socket destructors
When TX timestamping is enabled via SO_TIMESTAMPING, SKBs may be queued into sk_error_queue and will stay there until consumed. If userspace never gets to read the timestamps, or if the controller is removed unexpectedly, these SKBs will leak.
Fix by adding skb_queue_purge() calls for sk_error_queue in affected bluetooth destructors. RFCOMM does not currently use sk_error_queue.
From the CVE record · Linux
Bluetooth sockets in the Linux kernel can retain queued transmit timestamps when SO_TIMESTAMPING is enabled. Local userspace can leave those timestamps unread, causing a memory leak; the leak can also occur if a Bluetooth controller is removed unexpectedly. No further authentication requirement is specified.
Engineers running Linux kernels with Bluetooth support should check their versions; affected versions are not specified.