CVE-2024-58009

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.

Weakness

The product dereferences a pointer that it expects to be valid but is NULL.

Affected Software

Potential Mitigations

References

• https://git.kernel.org/stable/c/245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22
• https://git.kernel.org/stable/c/297ce7f544aa675b0d136d788cad0710cdfb0785
• https://git.kernel.org/stable/c/49c0d55d59662430f1829ae85b969619573d0fa1
• https://git.kernel.org/stable/c/5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1
• https://git.kernel.org/stable/c/691218a50c3139f7f57ffa79fb89d932eda9571e
• https://git.kernel.org/stable/c/8e605f580a97530e5a3583beea458a3fa4cbefbd
• https://git.kernel.org/stable/c/a9a7672fc1a0fe18502493936ccb06413ab89ea6
• https://git.kernel.org/stable/c/cf601a24120c674cd7c907ea695f92617af6abd0
• https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html