1. Home
  2. Vulnerabilities
  3. CVE-2024-58009
5.5
MEDIUM CVSS 3.1
CVE-2024-58009
Bluetooth: 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.

INFO

Published Date :

Feb. 27, 2025, 3:15 a.m.

Last Modified :

Nov. 3, 2025, 8:16 p.m.

Remotely Exploit :

No

Source :

416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products

The following products are affected by CVE-2024-58009 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Linux linux_kernel
: Total Affected Vendor : 1 | Products : 1
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 MEDIUM [email protected]
Solution
Update the Linux kernel to a version where the NULL sock pointer issue in L2CAP is resolved.
  • Apply the latest Linux kernel security updates.
  • Ensure all Bluetooth components are updated.
  • Verify system stability after the update.
References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2024-58009.

URL Resource
https://git.kernel.org/stable/c/245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22 Patch
https://git.kernel.org/stable/c/297ce7f544aa675b0d136d788cad0710cdfb0785 Patch
https://git.kernel.org/stable/c/49c0d55d59662430f1829ae85b969619573d0fa1 Patch
https://git.kernel.org/stable/c/5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1 Patch
https://git.kernel.org/stable/c/691218a50c3139f7f57ffa79fb89d932eda9571e Patch
https://git.kernel.org/stable/c/8e605f580a97530e5a3583beea458a3fa4cbefbd Patch
https://git.kernel.org/stable/c/a9a7672fc1a0fe18502493936ccb06413ab89ea6 Patch
https://git.kernel.org/stable/c/cf601a24120c674cd7c907ea695f92617af6abd0 Patch
https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2024-58009 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2024-58009 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2024-58009 vulnerability anywhere in the article.

Results are limited to the first 20 news articles due to potential performance issues.

The following table lists the changes that have been made to the CVE-2024-58009 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • CVE Modified by af854a3a-2127-422b-91ae-364da2661108

    Nov. 03, 2025

    Action Type Old Value New Value
    Added Reference https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html
  • Initial Analysis by [email protected]

    Oct. 22, 2025

    Action Type Old Value New Value
    Added CVSS V3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    Added CWE CWE-476
    Added CPE Configuration OR *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.13 up to (excluding) 6.13.3 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.1.120 up to (excluding) 6.1.129 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.10.231 up to (excluding) 5.10.235 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.15.174 up to (excluding) 5.15.179 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 5.4.287 up to (excluding) 5.4.291 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.12.5 up to (excluding) 6.12.14 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.6.66 up to (excluding) 6.6.78
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/297ce7f544aa675b0d136d788cad0710cdfb0785 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/49c0d55d59662430f1829ae85b969619573d0fa1 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/691218a50c3139f7f57ffa79fb89d932eda9571e Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/8e605f580a97530e5a3583beea458a3fa4cbefbd Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/a9a7672fc1a0fe18502493936ccb06413ab89ea6 Types: Patch
    Added Reference Type kernel.org: https://git.kernel.org/stable/c/cf601a24120c674cd7c907ea695f92617af6abd0 Types: Patch
  • CVE Modified by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Mar. 13, 2025

    Action Type Old Value New Value
    Added Reference https://git.kernel.org/stable/c/8e605f580a97530e5a3583beea458a3fa4cbefbd
    Added Reference https://git.kernel.org/stable/c/a9a7672fc1a0fe18502493936ccb06413ab89ea6
    Added Reference https://git.kernel.org/stable/c/cf601a24120c674cd7c907ea695f92617af6abd0
  • New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67

    Feb. 27, 2025

    Action Type Old Value New Value
    Added 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.
    Added Reference https://git.kernel.org/stable/c/245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22
    Added Reference https://git.kernel.org/stable/c/297ce7f544aa675b0d136d788cad0710cdfb0785
    Added Reference https://git.kernel.org/stable/c/49c0d55d59662430f1829ae85b969619573d0fa1
    Added Reference https://git.kernel.org/stable/c/5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1
    Added Reference https://git.kernel.org/stable/c/691218a50c3139f7f57ffa79fb89d932eda9571e
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.
Vulnerability Scoring Details
Base CVSS Score: 5.5
Attack Vector
Attack Complexity
Privileges Required
User Interaction
Scope
Confidentiality Impact
Integrity Impact
Availability Impact