Bluetooth: SMP: Fail if remote and local public keys are identical

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000522: Bluetooth: SMP: Fail if remote and local public keys are identical. Affects Kernel versions >= bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9, < d8d261c7cfb3a5dd921b4aeeb944718afc3f3961. 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 vulnerability affects the Kernel package in the Linux ecosystem. The Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for software to interact with the hardware. It plays a crucial role in the overall functionality and stability of the system. This vulnerability specifically targets the Bluetooth Secure Simple Pairing (SMP) protocol, which is used for establishing secure connections between Bluetooth devices. The vulnerability arises when the remote and local public keys in the SMP protocol are identical.

Vulnerability Detail

The vulnerability in the Bluetooth SMP protocol occurs when the remote and local public keys are the same. This can lead to potential security risks as it undermines the integrity and confidentiality of the communication between Bluetooth devices. An attacker could exploit this vulnerability to perform man-in-the-middle attacks, eavesdrop on sensitive data, or tamper with the communication. The impact and attack plausibility of this vulnerability have not been proven yet, but it is essential to address it to ensure the security of Bluetooth connections.

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 →

Conclusion

The Bluetooth: SMP: Fail if remote and local public keys are identical vulnerability affects the Kernel package in the Linux ecosystem. It can potentially compromise the security of Bluetooth connections, allowing attackers to perform various malicious activities. To mitigate this vulnerability, it is recommended to update the Linux Kernel package to version v5.10.40 or later. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can potentially compromise the security of Bluetooth connections, allowing attackers to perform man-in-the-middle attacks, eavesdrop on communication, or tamper with data.

You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.

No specific workaround has been provided for this vulnerability. It is recommended to update the Linux Kernel package to the latest version to fix the issue.

There is no evidence of this vulnerability being exploited in the wild. However, it is crucial to address it promptly to prevent potential security breaches.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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