Answer in brief
CVE-2024-58009 records a Unknown severity vulnerability in Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic), Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystem (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f6ad641646b67f29c7578dcd6c25813c7dcbf51e <a9a7672fc1a0fe18502493936ccb06413ab89ea6 || >=daa13175a6dea312a76099066cb4cbd4fc959a84 <8e605f580a97530e5a3583beea458a3fa4cbefbd || >=a8677028dd5123e5e525b8195483994d87123de4 <cf601a24120c674cd7c907ea695f92617af6abd0 || >=bb2f2342a6ddf7c04f9aefbbfe86104cd138e629 <297ce7f544aa675b0d136d788cad0710cdfb0785 || >=8ad09ddc63ace3950ac43db6fbfe25b40f589dd6 <245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22 || >=61686abc2f3c2c67822aa23ce6f160467ec83d35 <691218a50c3139f7f57ffa79fb89d932eda9571e || >=7c4f78cdb8e7501e9f92d291a7d956591bf73be9 <49c0d55d59662430f1829ae85b969619573d0fa1 || >=7c4f78cdb8e7501e9f92d291a7d956591bf73be9 <5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1 || >=5.4.287 <5.4.291 || >=5.10.231 <5.10.235 || >=5.15.174 <5.15.179 || >=6.1.120 <6.1.129 || >=6.6.66 <6.6.78 || >=6.12.5 <6.12.14 | a9a7672fc1a0fe18502493936ccb06413ab89ea6, 8e605f580a97530e5a3583beea458a3fa4cbefbd, cf601a24120c674cd7c907ea695f92617af6abd0, 297ce7f544aa675b0d136d788cad0710cdfb0785, 245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22, 691218a50c3139f7f57ffa79fb89d932eda9571e, 49c0d55d59662430f1829ae85b969619573d0fa1, 5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1, 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78, 6.12.14 |
| Linux/Linuxgeneric | 6.13 | Not reported |
| Siemens/SIMATIC S7-1500 TM MFP - GNU/Linux subsystemgeneric | >=0 <* | * |
Published upstream
Feb 27, 2025
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.