Critical Bluetooth Vulnerability in Linux Packages: Null Pointer Dereference Risk

linux Updated 02 Oct 2025

Summary

01/04/2025
N/A
Yes i
Medium
5.5

CVE-2025-21937: In the Linux kernel, the following vulnerability has been resolved: Bluetooth: Add check for mgmt_alloc_skb() in mgmt_remote_name() Add check for the return value of mgmt_alloc_skb() in mgmt_remote_name() to prevent null... Affects linux versions < 6.1.133-1. Fixed in 6.1.133-1. 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, including Debian. It manages hardware resources and provides essential services for software applications. This vulnerability affects the Bluetooth subsystem, which is responsible for wireless communication between devices. The specific issue arises from a lack of proper error handling in the mgmt_remote_name() function, potentially leading to system instability.

Vulnerability Detail

In the Linux kernel, a vulnerability was identified in the Bluetooth management functions. Specifically, the mgmt_remote_name() function did not adequately check the return value of mgmt_alloc_skb(), which could lead to a null pointer dereference. This flaw could allow an attacker to exploit the system, causing crashes or unexpected behavior, thereby compromising the integrity and availability of the system.

How To Fix

Minimum fixed version

6.1.133-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

Currently, there are no specific workarounds provided for this vulnerability. It is recommended to apply the patch as soon as it becomes available for Debian 12.

Conclusion

The CVE-2025-21937 vulnerability in the Linux kernel poses a significant risk due to its potential for causing system instability through null pointer dereference. Users are advised to update their systems promptly to mitigate this risk. Monitoring tools like Vulert can help track vulnerabilities in your software without requiring code access.

See every vulnerability recorded for linux →

Share this vulnerability

FAQ

CVE-2025-21937 is a vulnerability in the Linux kernel's Bluetooth subsystem that can lead to a null pointer dereference.

This vulnerability can cause system crashes or unexpected behavior, potentially allowing attackers to exploit the system.

Debian 12 is affected but does not yet have a fixed version. Debian 13 is affected but has a patched version available.

You can protect your system by updating to the latest patched version of the Linux package as soon as it is available.

More information can be found on the official CVE database or through security advisories from the Debian project.

Related vulnerabilities

Recent vulnerabilities recorded for linux.

How To Fix

Minimum fixed version

6.1.133-1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade linux

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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