Critical Use-After-Free Vulnerability in Linux Kernel Bluetooth RFCOMM - CVE-2024-56604

linux Updated 02 Oct 2025

Summary

27/12/2024
N/A
No i
High
7.8

CVE-2024-56604: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: RFCOMM: avoid leaving dangling sk pointer in rfcomm_sock_alloc() bt_sock_alloc() attaches allocated sk object to the provided sock object. Affects linux versions 5.10.103-1 – 6.9.9-1. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Linux kernel is a core component of many operating systems, providing essential services for hardware and software interaction. It supports various functionalities, including Bluetooth communication. The RFCOMM protocol is used for serial communication over Bluetooth, allowing devices to communicate wirelessly. This vulnerability affects the RFCOMM implementation, potentially leading to severe security issues if exploited.

Vulnerability Detail

In the Linux kernel, a vulnerability has been identified in the Bluetooth RFCOMM implementation, specifically in the function rfcomm_sock_alloc(). When allocating a socket, if the subsequent allocation of a data link connection (rfcomm_dlc_alloc()) fails, the socket pointer (sk) is released, but the pointer remains in the sock object, leading to a dangling pointer. This can result in a use-after-free condition, allowing an attacker to exploit the dangling pointer to execute arbitrary code or cause a denial of service.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

Currently, there are no specific workarounds mentioned for this vulnerability. The best course of action is to apply the available patches as soon as possible.

Conclusion

CVE-2024-56604 represents a significant security risk within the Linux kernel's Bluetooth RFCOMM implementation. Users are strongly advised to update their systems to the latest patched versions to protect against potential exploitation. Regular monitoring for vulnerabilities using tools like Vulert can help maintain system security.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2024-56604 is a critical vulnerability in the Linux kernel's Bluetooth RFCOMM implementation that can lead to use-after-free conditions.

Exploitation of this vulnerability can allow attackers to execute arbitrary code or cause a denial of service, compromising system integrity.

The vulnerability affects multiple versions of the Linux kernel across Debian 11, 12, and 13 distributions.

You can check if your application is affected by using the Vulert playground at Vulert Scanner, which monitors open-source vulnerabilities without requiring installation.

While there are no specific workarounds, it is crucial to prioritize updating your system to the patched version as soon as possible to mitigate risks.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback