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-1000526: Bluetooth: SMP: Fail if remote and local public keys are identical. Affects Kernel versions >= bfe01a5ba2490f299e1d2d5508cbbbadd897bbe9, < 6555a006b21ab49090b9a7b36e92d0421db19328. 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 operating system that manages system resources and provides an interface for software to interact with the hardware. It is responsible for tasks such as process management, memory management, and device drivers. The vulnerability specifically impacts the Bluetooth Secure Simple Pairing (SMP) protocol, which is used for establishing secure connections between Bluetooth devices.

Vulnerability Detail

The vulnerability occurs when the remote and local public keys in the Bluetooth SMP protocol are identical. This can lead to potential security risks, although the actual impact and attack plausibility have not been proven yet. The vulnerability was introduced in version v3.17 of the Linux Kernel and has been fixed in version v4.9.270. It is important to note that this vulnerability is specific to the Bluetooth SMP protocol and does not affect other aspects of the Kernel or Bluetooth functionality.

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

There is no specific workaround mentioned for this vulnerability. The recommended approach is to apply the fix by updating the Linux Kernel to the patched version.

Conclusion

The Bluetooth: SMP: Fail if remote and local public keys are identical vulnerability affects the Kernel package in the Linux ecosystem. It specifically impacts the Bluetooth Secure Simple Pairing (SMP) protocol. To mitigate the vulnerability, it is recommended to update the Linux Kernel to version v4.9.270 or later. For further support on vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is currently unknown as the actual attack plausibility has not been proven. However, it is important to apply the fix to ensure the security of Bluetooth connections.

You can use tools like Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert Playground allows you to analyze your manifest file, such as package-lock.json, and provides real-time alerts for open-source vulnerabilities.

The remote exploitation of this vulnerability has not been proven yet. However, it is always recommended to apply security patches and updates to mitigate potential risks.

No, only versions starting from v3.17 up to v4.9.269 are affected. The vulnerability has been fixed in version v4.9.270.

For more details about this vulnerability, you can refer to the source link provided in the vulnerability details section.

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