LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This Linux kernel Bluetooth flaw is a reliability and safety concern in the L2CAP code path. The source describes a NULL socket pointer reaching allocation/error handling logic. Business urgency depends on whether affected systems use Bluetooth and can receive vendor kernel updates.

Executive priority

Treat as a targeted patch-management item, not an emergency, unless Bluetooth is enabled on exposed or safety-sensitive systems. Prioritize laptops, embedded Linux, industrial devices, and appliances over headless servers with Bluetooth disabled.

Technical view

CVE-2024-58009 fixes l2cap_sock_alloc() handling when called from l2cap_sock_new_connection_cb() with a NULL sock pointer. Upstream stable commit references are provided for multiple kernel branches. No CVSS, CWE, or detailed impact rating is supplied in the bundle.

Likely exposure

Likely exposure is Linux systems running affected kernel ranges with Bluetooth/L2CAP enabled or reachable. Standard servers with Bluetooth disabled are likely lower priority. Debian LTS and Siemens references indicate downstream vendors tracked the issue, so validate packaged kernels and vendor appliances separately.

Exploitation context

The bundle does not show CISA KEV listing, active exploitation, or public exploit evidence. The described condition is a kernel Bluetooth error-handling flaw, but the sources do not prove practical remote exploitation or privilege escalation.

Researcher notes

Evidence is incomplete for severity and exploitability. The strongest source detail is the upstream kernel rationale: checking for NULL avoids exposing a dummy-initialized channel through global L2CAP paths. Avoid assigning impact beyond vendor statements.

Mitigation direction

  • Apply vendor kernel updates that include the referenced upstream stable fixes.
  • Check Debian LTS guidance for Debian-based systems.
  • Check Siemens SSA-265688 for affected Siemens-managed products.
  • Disable Bluetooth where it is not operationally required.
  • Track vendor advisories if no fix is available for an appliance.

Validation and detection

  • Inventory Linux kernels and compare against vendor-fixed package versions.
  • Confirm Bluetooth is disabled on systems that do not need it.
  • Verify updated kernels include the referenced stable commits or vendor backports.
  • Review downstream advisories for Debian and Siemens assets.
  • Monitor vendor security channels for revised severity or exploit information.
Prepared
Confidence
medium
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2024-58009 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
2ADP providers
11Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
siemens-SADPADP container

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf6ad641646b67f29c7578dcd6c25813c7dcbf51e, daa13175a6dea312a76099066cb4cbd4fc959a84, a8677028dd5123e5e525b8195483994d87123de4, bb2f2342a6ddf7c04f9aefbbfe86104cd138e629, 8ad09ddc63ace3950ac43db6fbfe25b40f589dd6, 61686abc2f3c2c67822aa23ce6f160467ec83d35, 7c4f78cdb8e7501e9f92d291a7d956591bf73be9, 7c4f78cdb8e7501e9f92d291a7d956591bf73be9, 5.4.287, 5.10.231, 5.15.174, 6.1.120, 6.6.66, 6.12.5unaffected
LinuxLinux6.13, 0, 5.4.291, 5.10.235, 5.15.179, 6.1.129, 6.6.78, 6.12.14, 6.13.3, 6.14affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.