# Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc

CVE record · `CVE-2024-58009`

- **Identifiers:** `CVE-2024-58009`
- **State:** Confirmed
- **Severity:** No CVSS score
- **Critical:** No
- **CNA:** Linux
- **Technologies:** [Linux kernel](https://agentprime.io/advisories/technology/linux-kernel.md)
- **Published:** 27 Feb 2025
- **Updated:** 15 Oct 2026
- **Reviewed by a person:** No

Published by the CVE Program (CNA: Linux) at 27 Feb 2025, 02:12 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it.

## Affected products, as the CNA wrote them

- Vendor: Linux. Product: Linux.
  - affected: `f6ad641646b67f29c7578dcd6c25813c7dcbf51e to before a9a7672fc1a0fe18502493936ccb06413ab89ea6` (git)
  - affected: `daa13175a6dea312a76099066cb4cbd4fc959a84 to before 8e605f580a97530e5a3583beea458a3fa4cbefbd` (git)
  - affected: `a8677028dd5123e5e525b8195483994d87123de4 to before cf601a24120c674cd7c907ea695f92617af6abd0` (git)
  - affected: `bb2f2342a6ddf7c04f9aefbbfe86104cd138e629 to before 297ce7f544aa675b0d136d788cad0710cdfb0785` (git)
  - affected: `8ad09ddc63ace3950ac43db6fbfe25b40f589dd6 to before 245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22` (git)
  - affected: `61686abc2f3c2c67822aa23ce6f160467ec83d35 to before 691218a50c3139f7f57ffa79fb89d932eda9571e` (git)
  - affected: `7c4f78cdb8e7501e9f92d291a7d956591bf73be9 to before 49c0d55d59662430f1829ae85b969619573d0fa1` (git)
  - affected: `7c4f78cdb8e7501e9f92d291a7d956591bf73be9 to before 5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1` (git)
  - affected: `5.4.287 to before 5.4.291` (semver)
  - affected: `5.10.231 to before 5.10.235` (semver)
  - affected: `5.15.174 to before 5.15.179` (semver)
  - affected: `6.1.120 to before 6.1.129` (semver)
  - and 2 more
  - Other versions: unaffected
- Vendor: Linux. Product: Linux.
  - affected: `6.13`
  - unaffected: `before 6.13` (semver)
  - unaffected: `5.4.291 to 5.4.*, inclusive` (semver)
  - unaffected: `5.10.235 to 5.10.*, inclusive` (semver)
  - unaffected: `5.15.179 to 5.15.*, inclusive` (semver)
  - unaffected: `6.1.129 to 6.1.*, inclusive` (semver)
  - unaffected: `6.6.78 to 6.6.*, inclusive` (semver)
  - unaffected: `6.12.14 to 6.12.*, inclusive` (semver)
  - unaffected: `6.13.3 to 6.13.*, inclusive` (semver)
  - unaffected: `6.14 to *, inclusive` (original_commit_for_fix)
  - Other versions: affected

## Not analysed yet

We haven’t published our own analysis of this CVE. If a person reviews it, this page will say what’s affected and what has to be true for it to matter.

## Severity and exploitation

No source has published a CVSS score for this record yet.

- **CISA KEV:** Not listed.
- **EPSS:** 0.0021, the 10th percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the CVE Program, published 27 Feb 2025. New records show when each source confirmed them.

## Sources

- [CVE List: CVE-2024-58009](https://www.cve.org/CVERecord?id=CVE-2024-58009)
- [NVD: CVE-2024-58009](https://nvd.nist.gov/vuln/detail/CVE-2024-58009)

### References from the CNA

- <https://git.kernel.org/stable/c/a9a7672fc1a0fe18502493936ccb06413ab89ea6>
- <https://git.kernel.org/stable/c/8e605f580a97530e5a3583beea458a3fa4cbefbd>
- <https://git.kernel.org/stable/c/cf601a24120c674cd7c907ea695f92617af6abd0>
- <https://git.kernel.org/stable/c/297ce7f544aa675b0d136d788cad0710cdfb0785>
- <https://git.kernel.org/stable/c/245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22>
- <https://git.kernel.org/stable/c/691218a50c3139f7f57ffa79fb89d932eda9571e>
- <https://git.kernel.org/stable/c/49c0d55d59662430f1829ae85b969619573d0fa1>
- <https://git.kernel.org/stable/c/5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1>

Facts on this page come from the CVE List as the CNA published them, with CVSS from the sources named above, CISA KEV and FIRST EPSS. Vendors, products and versions are shown as the CNA wrote them. We don’t reproduce the CVE’s description.

## Check whether this affects you

This CVE names a vendor and product rather than a package, so the lockfile check doesn’t match it. Compare the affected versions above with what you run.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), `get_advisory` returns this record and `search_advisories` finds related ones. Setup: <https://agentprime.io/mcp.md>
- As JSON: <https://api.agentprime.io/v1/advisories/CVE-2024-58009>
- Everything that needs attention now: <https://agentprime.io/advisories/critical.md>

---

The web page: <https://agentprime.io/advisories/CVE-2024-58009/>. Everything for agents: <https://agentprime.io/llms.txt>.
