CVE-2024-58009 In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: handle NULL sock pointer in…
Description
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.
Affected products and versions
| Product | Affected versions | Fixed in |
|---|---|---|
| Linux 6.14 | earliest → < 6.14 | 6.14 |
| Linux | 6.13 | 6.13.3 |
| Linux 6.12 | earliest → < 6.12.14 | 6.12.14 |
| Linux 6.6 | earliest → < 6.6.78 | 6.6.78 |
| Linux 6.1 | earliest → < 6.1.129 | 6.1.129 |
| Linux 5.15 | earliest → < 5.15.179 | 5.15.179 |
| Linux 5.10 | earliest → < 5.10.235 | 5.10.235 |
| Linux 5.4 | earliest → < 5.4.291 | 5.4.291 |
| SIMATIC S7-1500 TM MFP - GNU/Linux subsystem | Versions not published |