CVE-2020-26558: Medium severity Google Android vulnerability

Published Jan 21, 2021
·
Updated

A vulnerability was found in Linux Kernel, where Passkey Entry protocol used in Secure Simple Pairing (SSP), Secure Connections (SC) and LE Secure Connections (LESC) of the Bluetooth Core Specification is vulnerable to an impersonation attack where an active attacker can impersonate the initiating device without any previous knowledge.

Refer: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=6d19628f539fccf899298ff02ee4c73e4bf6df3f

Other sources

A vulnerability was found in the bluez, where Passkey Entry protocol used in Secure Simple Pairing (SSP), Secure Connections (SC) and LE Secure Connections (LESC) of the Bluetooth Core Specification is vulnerable to an impersonation attack where an active attacker can impersonate the initiating device without any previous knowledge.

Bluetooth LE and BR/EDR secure pairing in Bluetooth Core Specification 2.1 through 5.2 may permit a nearby man-in-the-middle attacker to identify the Passkey used during pairing (in the Passkey authentication procedure) by reflection of the public key and the authentication evidence of the initiating device, potentially permitting this attacker to complete authenticated pairing with the responding device using the correct Passkey for the pairing session. The attack methodology determines the Passkey value one bit at a time.

Affected Software

69 affected componentsFixes available
redhat/bluez<0:5.56-1.el8
0:5.56-1.el8
redhat/bluez<5.57
5.57
Google Android
Bluetooth Bluetooth Core Specification>=2.1<=5.2
Fedoraproject Fedora=34
Debian Debian Linux=9.0
Linux Linux kernel<5.13
All of the following
Intel Ax210 Firmware
Intel Ax210
All of the following
Intel Ax201 Firmware
Intel Ax201
All of the following
Intel Ax200 Firmware
Intel Ax200
All of the following
Intel Ac 9560 Firmware
Intel Ac 9560
All of the following
Intel Ac 9462 Firmware
Intel Ac 9462
All of the following
Intel Ac 9461 Firmware
Intel Ac 9461
All of the following
Intel Ac 9260 Firmware
Intel Ac 9260
All of the following
Intel Ac 8265 Firmware
Intel Ac 8265
All of the following
Intel Ac 8260 Firmware
Intel Ac 8260
All of the following
Intel Ac 3168 Firmware
Intel Ac 3168
All of the following
Intel Ac 7265 Firmware
Intel Ac 7265
All of the following
Intel Ac 3165 Firmware
Intel Ac 3165
All of the following
Intel Ax1675 Firmware
Intel Ax1675
All of the following
Intel Ax1650 Firmware
Intel Ax1650
All of the following
Intel Ac 1550 Firmware
Intel Ac 1550
Intel Ax210 Firmware
Intel Ax210
Intel Ax201 Firmware
Intel Ax201
Intel Ax200 Firmware
Intel Ax200
Intel Ac 9560 Firmware
Intel Ac 9560
Intel Ac 9462 Firmware
Intel Ac 9462
Intel Ac 9461 Firmware
Intel Ac 9461
Intel Ac 9260 Firmware
Intel Ac 9260
Intel Ac 8265 Firmware
Intel Ac 8265
Intel Ac 8260 Firmware
Intel Ac 8260
Intel Ac 3168 Firmware
Intel Ac 3168
Intel Ac 7265 Firmware
Intel Ac 7265
Intel Ac 3165 Firmware
Intel Ac 3165
Intel Ax1675 Firmware
Intel Ax1675
Intel Ax1650 Firmware
Intel Ax1650
Intel Ac 1550 Firmware
Intel Ac 1550
debian/bluez
5.55-3.1+deb11u15.55-3.1+deb11u25.66-1+deb12u25.66-1+deb12u15.82-1
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.25-16.12.27-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/bluez to a version that resolves this vulnerability.

    Fixed in 0:5.56-1.el8
  2. Upgrade

    Upgrade debian/bluez to a version that resolves this vulnerability.

    Fixed in 5.55-3.1+deb11u1Fixed in 5.55-3.1+deb11u2Fixed in 5.66-1+deb12u2Fixed in 5.66-1+deb12u1Fixed in 5.82-1
  3. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1Fixed in 6.12.27-1
  4. Upgrade

    Upgrade redhat/bluez to a version that resolves this vulnerability.

    Fixed in 5.57
  5. Upgrade

    Upgrade redhat/bluez to a version that resolves this vulnerability.

    Fixed in 5.58
  6. Upgrade

    Upgrade debian/bluez to a version that resolves this vulnerability.

    Fixed in 5.55-3.1+deb11u1
  7. Upgrade

    Upgrade debian/bluez to a version that resolves this vulnerability.

    Fixed in 5.55-3.1+deb11u2
  8. Upgrade

    Upgrade debian/bluez to a version that resolves this vulnerability.

    Fixed in 5.66-1+deb12u2
  9. Upgrade

    Upgrade debian/bluez to a version that resolves this vulnerability.

    Fixed in 5.66-1+deb12u1
  10. Upgrade

    Upgrade debian/bluez to a version that resolves this vulnerability.

    Fixed in 5.82-1
  11. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.223-1
  12. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 5.10.234-1
  13. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.129-1
  14. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.1.135-1
  15. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.25-1
  16. Upgrade

    Upgrade debian/linux to a version that resolves this vulnerability.

    Fixed in 6.12.27-1

Event History

Jan 21, 2021
Data Sourced
via Red Hat·08:03 AM
DescriptionSeverityAffected Software
May 24, 2021
CVE Published
04:00 PM
CVE Published
via MITRE·05:22 PM
Data Sourced
via MITRE·05:22 PM
Description
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeaknessAffected Software
Jun 7, 2021
Data Sourced
via Android·12:00 AM
SeverityAffected Software
Jan 11, 2024
Data Sourced
via Launchpad·11:47 PM
Description
May 6, 2025
Data Sourced
via Ubuntu·04:24 AM
RemedyDescriptionSeverityAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Frequently Asked Questions

1

What is the severity of CVE-2020-26558?

CVE-2020-26558 is classified as a high severity vulnerability due to the potential for active impersonation attacks.

2

How do I fix CVE-2020-26558?

To fix CVE-2020-26558, update the affected software packages to the specified versions or later, such as bluez version 5.57 or higher.

3

What software is affected by CVE-2020-26558?

CVE-2020-26558 affects various versions of the bluez package and the Linux kernel, among others that implement Bluetooth Core Specification.

4

What type of attack is associated with CVE-2020-26558?

CVE-2020-26558 is associated with impersonation attacks that can be executed by an active attacker during Bluetooth pairing processes.

5

Is CVE-2020-26558 limited to specific operating systems?

CVE-2020-26558 impacts multiple operating systems including those using specific versions of the Linux Kernel and bluez packages.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203