CVE-2024-56604

Kernel memory corruption via dangling RFCOMM pointer

Published Dec 27, 2024 · Updated Aug 5, 2026

Use-after-free in Linux kernel Bluetooth RFCOMM allows local users to trigger unsafe reuse of a freed socket after allocation failure. The rfcomm_sock_alloc() path attaches the newly allocated sk object to sock before rfcomm_dlc_alloc(); if DLC allocation fails, it releases sk without clearing the pointer. Local low-privileged access and an rfcomm_dlc_alloc() failure are required; reuse of the dangling pointer can compromise kernel memory and interrupt the system.

CVSS severity7.8
High
EPSS probability0.22%
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 Linux kernel Bluetooth RFCOMM allows local users to trigger unsafe reuse of a freed socket after allocation failure. The rfcomm_sock_alloc() path attaches the newly allocated sk object to sock before rfcomm_dlc_alloc(); if DLC allocation fails, it releases sk without clearing the pointer. Local low-privileged access and an rfcomm_dlc_alloc() failure are required; reuse of the dangling pointer can compromise kernel memory and interrupt the system.

The record

CVE
CVE-2024-56604
Published
Dec 27, 2024
Updated
Aug 5, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
CWE-416, T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Dec 27, 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=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <32df687e129ef0f9afcbcc914f7c32deb28fd481
  2. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3945c799f12b8d1f49a3b48369ca494d981ac465
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6021ccc2471b7b95e29b7cfc7938e042bf56e281
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ac3eaac4cf142a15fe67be747a682b1416efeb6e
  5. Affected versionversion=2.6.12

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <32df687e129ef0f9afcbcc914f7c32deb28fd481; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <3945c799f12b8d1f49a3b48369ca494d981ac465; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6021ccc2471b7b95e29b7cfc7938e042bf56e281; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <ac3eaac4cf142a15fe67be747a682b1416efeb6e; version=2.6.12

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
7.8CISA-ADPCVSS:3.1/AV:L/AC:L/PR:L/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 9, 2026Sep 15, 2026
Latest reporting daySep 15, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-416Use After Free
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