Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()
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 |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc()
bt_sock_alloc() attaches allocated sk object to the provided sock object. If rfcomm_dlc_alloc() fails, we release the sk object, but leave the dangling pointer in the sock object, which may cause use-after-free.
Fix this by swapping calls to bt_sock_alloc() and rfcomm_dlc_alloc().
From the CVE record · Linux
The Linux kernel’s Bluetooth RFCOMM socket allocation can leave a dangling pointer if rfcomm_dlc_alloc() fails, potentially causing a use-after-free. The input does not specify how an attacker could trigger the failure or whether authentication or user interaction is required.
Engineers running the Linux kernel should check their versions; affected versions are not specified in the input.