CVE-2024-41062

Kernel compromise via unlocked L2CAP receive callback

Published Jul 29, 2024 · Updated Aug 5, 2026

Use-after-free in the Linux kernel allows physically proximate attackers to compromise affected systems over Bluetooth. The L2CAP connectionless receive path can enter l2cap_sock_recv_cb after concurrent socket teardown frees the socket, and the callback dereferences the stale pointer without holding the channel mutex. An unpaired Bluetooth peer within radio range can drive the receive side without user interaction, leading to kernel memory disclosure, modification, or a crash.

CVSS severity8.8
High
EPSS probability0.31%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Use-after-free in the Linux kernel allows physically proximate attackers to compromise affected systems over Bluetooth. The L2CAP connectionless receive path can enter l2cap_sock_recv_cb after concurrent socket teardown frees the socket, and the callback dereferences the stale pointer without holding the channel mutex. An unpaired Bluetooth peer within radio range can drive the receive side without user interaction, leading to kernel memory disclosure, modification, or a crash.

The record

CVE
CVE-2024-41062
Published
Jul 29, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1068
Attack vector
adjacent
Privileges
unauthenticated

Timeline

How it unfolded

  1. Jul 29, 2024CVE publishedPublication date reported by the CVE source.
  2. Aug 5, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=3.4
  2. Affected versionversion=5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa <3b732449b78183d17178db40be3a4401cf3cd629
  3. Affected versionversion=5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa <605572e64cd9cebb05ed609d96cff05b50d18cdf
  4. Affected versionversion=5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa <89e856e124f9ae548572c56b1b70c2255705f8fe
  5. Affected versionversion=5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa <b803f30ea23e0968b6c8285c42adf0d862ab2bf6

What conditions does exploitation require?

Attack vectoradjacent
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=3.4; version=5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa <3b732449b78183d17178db40be3a4401cf3cd629; version=5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa <605572e64cd9cebb05ed609d96cff05b50d18cdf; version=5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa <89e856e124f9ae548572c56b1b70c2255705f8fe; version=5b4cedaa14bd1fe3ca1d59c684203a6ae7747faa <b803f30ea23e0968b6c8285c42adf0d862ab2bf6

Published CVSS scores

5.5UbuntuCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
8.8Linux kernel CNACVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectoradjacent
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo