# CVE-2024-41062: bluetooth/l2cap: sync sock recv cb and release

> A race condition in the Linux kernel Bluetooth L2CAP subsystem allows a use-after-free, potentially causing a system crash.

- **Severity:** High 8.8 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Jul 2024
- **Updated:** 3 Oct 2026
- **Also known as:** BELL-CVE-2024-41062, DEBIAN-CVE-2024-41062, GHSA-f6q4-wr98-4jf5, ROOT-OS-DEBIAN-11-CVE-2024-41062, ROOT-OS-UBUNTU-2204-CVE-2024-41062, SUSE-SU-2025:1104-1, SUSE-SU-2025:1120-1, UBUNTU-CVE-2024-41062

## What is CVE-2024-41062?

CVE-2024-41062 is a high-severity vulnerability in Linux kernel, published on 29 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In the Linux kernel, the following vulnerability has been resolved:

bluetooth/l2cap: sync sock recv cb and release

The problem occurs between the system call to close the sock and hci_rx_work,
where the former releases the sock and the latter accesses it without lock protection.

           CPU0                       CPU1
           ----                       ----
           sock_close                 hci_rx_work
	   l2cap_sock_release         hci_acldata_packet
	   l2cap_sock_kill            l2cap_recv_frame
	   sk_free                    l2cap_conless_channel
	                              l2cap_sock_recv_cb

If hci_rx_work processes the data that needs to be received before the sock is
closed, then everything is normal; Otherwise, the work thread may access the
released sock when receiving data.

Add a chan mutex in the rx callback of the sock to achieve synchronization between
the sock release and recv cb.

Sock is dead, so set chan data to NULL, avoid others use invalid sock pointer.

## Which versions are affected by CVE-2024-41062?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kernel-livepatch-SLE15-SP4_Update_24` | SUSE:Linux Enterprise Live Patching 15 SP4 | All versions | 15-150400.2.1 |
| `kernel-livepatch-SLE15-SP4_Update_25` | SUSE:Linux Enterprise Live Patching 15 SP4 | All versions | 15-150400.2.1 |
| `kernel-livepatch-SLE15-SP5_Update_12` | SUSE:Linux Enterprise Live Patching 15 SP5 | All versions | 15-150500.2.1 |
| `kernel-livepatch-SLE15-SP5_Update_13` | SUSE:Linux Enterprise Live Patching 15 SP5 | All versions | 13-150500.2.1 |

Products: Linux kernel.

## How do I fix CVE-2024-41062?

Apply the vendor's patch.

## Is CVE-2024-41062 being exploited?

There is no known exploitation of CVE-2024-41062 in the wild and no public exploit code.

## Other vulnerabilities in Linux kernel

- [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild)
- [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild)
- [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild)
- [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-41062 and fix it if it is affected.

What it is: CVE-2024-41062 is a high-severity vulnerability in Linux kernel, published on 29 Jul 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-41062 in the wild and no public exploit code.

Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-41062/ (Markdown: https://insights.sbomify.com/CVE-2024-41062/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-41062
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-41062
- OSV: https://osv.dev/vulnerability/CVE-2024-41062

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-41062/
Summaries are generated and may contain mistakes; the official description above is the record.