Bluetooth: coredump: Quiesce dump work on unregister
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: coredump: Quiesce dump work on unregister
hci_devcd_handle_pkt_init() arms dump_timeout and coredump producers queue dump_rx without holding an hdev reference. Unregister leaves both works live, so disconnecting during an active dump lets them access hdev after hci_release_dev() frees it.
Shut down coredump processing during unregister. Close the producer gate under dump_q.lock before disabling both works, then free the active buffer and queued packets under hci_dev_lock. Serializing the gate with enqueue prevents controller-specific workers from adding packets after the final purge.
From the CVE record · Linux
The Linux kernel’s Bluetooth coredump handling can leave work queued after a device is unregistered. If a device disconnects during an active dump, that work can access the device after it has been freed; the input does not specify an attack path or authentication requirements.
Engineers running the Linux kernel should check whether their version includes the Bluetooth coredump unregister fix; affected versions are not specified.