Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 61686abc2f3c2c67822aa23ce6f160467ec83d35 · < 691218a50c3139f7f57ffa79fb89d932eda9571e| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc
A NULL sock pointer is passed into l2cap_sock_alloc() when it is called from l2cap_sock_new_connection_cb() and the error handling paths should also be aware of it.
Seemingly a more elegant solution would be to swap bt_sock_alloc() and l2cap_chan_create() calls since they are not interdependent to that moment but then l2cap_chan_create() adds the soon to be deallocated and still dummy-initialized channel to the global list accessible by many L2CAP paths. The channel would be removed from the list in short period of time but be a bit more straight-forward here and just check for NULL instead of changing the order of function calls.
Found by Linux Verification Center (linuxtesting.org) with SVACE static analysis tool.
From the CVE record · Linux
The Linux kernel’s Bluetooth L2CAP code can pass a NULL socket pointer to l2cap_sock_alloc(), whose error-handling paths do not account for it. This could cause a NULL pointer dereference when that path is reached; the input does not establish whether an attacker can trigger it or what access would be required.
Engineers running Linux kernels with Bluetooth L2CAP should check their kernel versions against the vendor advisory; affected versions were not provided.