Use After Free Vulnerability in Bluetooth: hci_send_acl

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1002316: Bluetooth: Fix use after free in hci_send_acl. Affects Kernel versions < 684e505406abaeabe0058e9776f9210bf2747953. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The Bluetooth vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the operating system that manages system resources and provides an interface for communication between hardware and software. Bluetooth is a wireless technology used for short-range communication between devices. The hci_send_acl function in the Kernel is responsible for sending data packets over the Bluetooth HCI (Host Controller Interface).

Vulnerability Detail

The use after free vulnerability in hci_send_acl occurs when the function continues to use a memory block after it has been freed. This can lead to various security issues, including the potential for remote code execution or denial of service attacks. An attacker could exploit this vulnerability by sending specially crafted Bluetooth packets, causing the Kernel to access freed memory and potentially execute arbitrary code or crash the system. The vulnerability has been fixed in Linux Kernel version v4.19.238 by commit 684e505406abaeabe0058e9776f9210bf2747953.

How To Fix

No fixed version is published for this vulnerability.

To fix the vulnerability, it is recommended to update the Linux Kernel to version v4.19.238 or later. This can be done by downloading the updated Kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the provided instructions. After updating the Kernel, it is important to reboot the system to apply the changes.

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

Workaround

There is no specific workaround mentioned for this vulnerability. Updating the Kernel to the fixed version is the recommended solution.

Conclusion

The use after free vulnerability in hci_send_acl of the Bluetooth implementation in the Kernel package poses a potential security risk. It is crucial to update the Linux Kernel to version v4.19.238 or later to mitigate this vulnerability. By doing so, the system will be protected against possible remote code execution or denial of service attacks. For additional support and guidance, please reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability could potentially allow an attacker to execute arbitrary code or crash the system by exploiting the use after free issue in hci_send_acl.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and Vulert will analyze it for any open-source vulnerabilities, including this Bluetooth vulnerability.

At the time of this report, no known exploits have been reported for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.

Yes, this vulnerability can be exploited remotely by sending specially crafted Bluetooth packets to the affected system.

For further support on vulnerability remediation, you can contact info@devnack.com. They can provide guidance and assistance in fixing the vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix the vulnerability, it is recommended to update the Linux Kernel to version v4.19.238 or later. This can be done by downloading the updated Kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the provided instructions. After updating the Kernel, it is important to reboot the system to apply the changes.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.