---
id: CVE-2024-58009
title: |-
  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_c…
summary: |-
  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_c…
severity: medium
cvss: 5.5
cvssVector: 'CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H'
cwe:
  - CWE-476
vendor: linux
product: linux_kernel
affected:
  - 'linux_kernel >= 5.4.287, < 5.4.291'
  - 'linux_kernel >= 5.10.231, < 5.10.235'
  - 'linux_kernel >= 5.15.174, < 5.15.179'
  - 'linux_kernel >= 6.1.120, < 6.1.129'
  - 'linux_kernel >= 6.6.66, < 6.6.78'
  - 'linux_kernel >= 6.12.5, < 6.12.14'
  - 'linux_kernel >= 6.13, < 6.13.3'
patched:
  - linux_kernel 6.13.3
published: '2025-02-27'
updated: '2026-10-15'
sourceUpdated: '2026-10-15T02:17:17.663'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2024-58009'
references:
  - url: 'https://git.kernel.org/stable/c/245d48c1ba3e7a1779c2f4cbc6f581ddc8a78e22'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/297ce7f544aa675b0d136d788cad0710cdfb0785'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/49c0d55d59662430f1829ae85b969619573d0fa1'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/5f397409f8ee5bc82901eeaf799e1cbc4f8edcf1'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/691218a50c3139f7f57ffa79fb89d932eda9571e'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/8e605f580a97530e5a3583beea458a3fa4cbefbd'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/a9a7672fc1a0fe18502493936ccb06413ab89ea6'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://git.kernel.org/stable/c/cf601a24120c674cd7c907ea695f92617af6abd0'
    label: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
  - url: 'https://lists.debian.org/debian-lts-announce/2025/03/msg00028.html'
    label: af854a3a-2127-422b-91ae-364da2661108
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-265688.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
  - url: 'https://cert-portal.siemens.com/productcert/html/ssa-784472.html'
    label: 0b142b55-0307-4c5a-b3c9-f314f3fb7c5e
tags:
  - nvd
  - cve.org
epss: 0.00206
epssPercentile: 0.10509
ingestedAt: '2026-10-15T03:30:12.791Z'
---

## Overview

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.

## Affected

- `linux_kernel >= 5.4.287, < 5.4.291`
- `linux_kernel >= 5.10.231, < 5.10.235`
- `linux_kernel >= 5.15.174, < 5.15.179`
- `linux_kernel >= 6.1.120, < 6.1.129`
- `linux_kernel >= 6.6.66, < 6.6.78`
- `linux_kernel >= 6.12.5, < 6.12.14`
- `linux_kernel >= 6.13, < 6.13.3`

## Remediation

Upgrade past the affected range:

- `linux_kernel 6.13.3`