Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2024-58009Bluetooth: L2CAP: handle NULL sock pointer in l2cap_sock_alloc

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.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 20 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2024-58009, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (13 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected f6ad641646b67f29c7578dcd6c25813c7dcbf51e – < a9a7672fc1a0fe18502493936ccb06413ab89ea6
    • affected daa13175a6dea312a76099066cb4cbd4fc959a84 – < 8e605f580a97530e5a3583beea458a3fa4cbefbd
    • affected a8677028dd5123e5e525b8195483994d87123de4 – < cf601a24120c674cd7c907ea695f92617af6abd0
    • affected bb2f2342a6ddf7c04f9aefbbfe86104cd138e629 – < 297ce7f544aa675b0d136d788cad0710cdfb0785
    • affected 8ad09ddc63ace3950ac43db6fbfe25b40f589dd6 – < 245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22
    • affected 61686abc2f3c2c67822aa23ce6f160467ec83d35 – < 691218a50c3139f7f57ffa79fb89d932eda9571e
    • affected 7c4f78cdb8e7501e9f92d291a7d956591bf73be9 – < 49c0d55d59662430f1829ae85b969619573d0fa1
    • affected 7c4f78cdb8e7501e9f92d291a7d956591bf73be9 – < 5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1
    • affected 5.4.287 – < 5.4.291
    • affected 5.10.231 – < 5.10.235
    • affected 5.15.174 – < 5.15.179
    • affected 6.1.120 – < 6.1.129
    • affected 6.6.66 – < 6.6.78
    • affected 6.12.5 – < 6.12.14

  • Linux · Linux

    • affected 6.13
    • unaffected < 6.13
    • unaffected 5.4.291 – ≤ 5.4.*
    • unaffected 5.10.235 – ≤ 5.10.*
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.129 – ≤ 6.1.*
    • unaffected 6.6.78 – ≤ 6.6.*
    • unaffected 6.12.14 – ≤ 6.12.*
    • unaffected 6.13.3 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References11

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2024-58009 badge
[![CVE-2024-58009](https://cveledger.app/badge/CVE-2024-58009.svg)](https://cveledger.app/cve/CVE-2024-58009)

Record last updated .