Memory Corruption Vulnerability in Linux Kernel Bluetooth Handling

linux Updated 02 Oct 2025

Summary

26/02/2025
N/A
No i
Unrated
Not published

CVE-2022-49138: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_event: Ignore multiple conn complete events When one of the three connection complete events is received multiple times for the same hand... 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 Penetration testing for web, API and mobile 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 the core component of many operating systems, providing essential services for all other parts of the system. It manages hardware resources, system calls, and provides a platform for applications to run. The kernel's Bluetooth subsystem facilitates wireless communication with Bluetooth devices. However, it is susceptible to vulnerabilities that can lead to severe issues, including memory corruption, which can compromise system stability and security.

Vulnerability Detail

In the Linux kernel, a vulnerability has been identified in the Bluetooth subsystem where multiple connection complete events for the same handle can lead to memory corruption. This occurs when the device is registered multiple times, causing subsequent events for a single connection to be ignored. The introduction of HCI_CONN_HANDLE_UNSET helps identify new connections, while checks for invalid handles (HCI_CONN_HANDLE_MAX) are implemented to mitigate this issue. The vulnerability can lead to unpredictable behavior and potential system crashes.

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 provided for this vulnerability. It is recommended to apply the patch as soon as it is available to prevent potential exploitation.

Conclusion

The CVE-2022-49138 vulnerability in the Linux kernel's Bluetooth subsystem poses a significant risk of memory corruption due to improper handling of connection events. Users are strongly advised to update their kernel to the latest patched version to ensure system stability and security. Monitoring tools like Vulert can assist in identifying vulnerabilities in your software.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2022-49138 is a vulnerability in the Linux kernel's Bluetooth subsystem that can lead to memory corruption due to multiple connection complete events being processed for the same handle.

This vulnerability can cause memory corruption, leading to system instability, crashes, or unexpected behavior when using Bluetooth devices.

If you are using Debian 11, 12, or 13 with an unpatched version of the Linux kernel, your system may be vulnerable to this issue.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. By using the Vulert playground, you can check if your application is affected by this vulnerability without needing to sign up.

While there are no specific workarounds, it is crucial to prioritize updating your kernel to the patched version as soon as possible to mitigate the risk of exploitation.

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