Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel a9a7672fc1a0fe18502493936ccb06413ab89ea6, Kernel 691218a50c3139f7f57ffa79fb89d932eda9571e, Kernel 49c0d55d59662430f1829ae85b969619573d0fa1 and 12 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=f6ad641646b67f29c7578dcd6c25813c7dcbf51e <a9a7672fc1a0fe18502493936ccb06413ab89ea6, >=61686abc2f3c2c67822aa23ce6f160467ec83d35 <691218a50c3139f7f57ffa79fb89d932eda9571e, >=7c4f78cdb8e7501e9f92d291a7d956591bf73be9 <49c0d55d59662430f1829ae85b969619573d0fa1, >=7c4f78cdb8e7501e9f92d291a7d956591bf73be9 <5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1, >=8ad09ddc63ace3950ac43db6fbfe25b40f589dd6 <245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22, >=a8677028dd5123e5e525b8195483994d87123de4 <cf601a24120c674cd7c907ea695f92617af6abd0, >=bb2f2342a6ddf7c04f9aefbbfe86104cd138e629 <297ce7f544aa675b0d136d788cad0710cdfb0785, >=daa13175a6dea312a76099066cb4cbd4fc959a84 <8e605f580a97530e5a3583beea458a3fa4cbefbd, =6.13, >=5.10.231 <5.10.235, >=5.15.174 <5.15.179, >=5.4.287 <5.4.291, >=6.1.120 <6.1.129, >=6.12.5 <6.12.14, >=6.6.66 <6.6.78 | a9a7672fc1a0fe18502493936ccb06413ab89ea6, 691218a50c3139f7f57ffa79fb89d932eda9571e, 49c0d55d59662430f1829ae85b969619573d0fa1, 5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1, 245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22, cf601a24120c674cd7c907ea695f92617af6abd0, 297ce7f544aa675b0d136d788cad0710cdfb0785, 8e605f580a97530e5a3583beea458a3fa4cbefbd, 5.10.235, 5.15.179, 5.4.291, 6.1.129, 6.12.14, 6.6.78 |
| linux-kernel: Kernel | >=5.15.174 <5.15.179, >=5.4.287 <5.4.291, >=6.1.120 <6.1.129, >=6.12.5 <6.12.14, >=6.13.0 <6.13.3, >=6.6.66 <6.6.78, >=5.10.231 <5.10.235 | 5.15.179, 5.4.291, 6.1.129, 6.12.14, 6.13.3, 6.6.78, 5.10.235 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket