Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 49dfbb9129c4edb318578de35cc45c555df37884 · < 61686abc2f3c2c67822aa23ce6f160467ec83d35| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: do not leave dangling sk pointer on error in l2cap_sock_create()
bt_sock_alloc() allocates the sk object and attaches it to the provided sock object. On error l2cap_sock_alloc() frees the sk object, but the dangling pointer is still attached to the sock object, which may create use-after-free in other code.
From the CVE record · Linux
The Linux kernel’s Bluetooth L2CAP socket creation code can leave a dangling pointer when socket allocation fails. If other code accesses that pointer, it may cause a use-after-free. The input does not specify whether exploitation requires network or local access, authentication, or user interaction.
Teams running the Linux kernel should check their versions; affected versions are not specified.