CVE-2024-26903: Bluetooth: rfcomm: Fix null-ptr-deref in rfcomm_check_security

Published Apr 17, 2024
·
Updated

Bluetooth: rfcomm: Fix null-ptr-deref in rfcommchecksecurity

Affected Software

18 affected componentsFixes available
Linux Linux kernel<4.19.311
Linux Linux kernel>=4.20<5.4.273
Linux Linux kernel>=5.5<5.10.214
Linux Linux kernel>=5.11<5.15.153
Linux Linux kernel>=5.16<6.1.83
Linux Linux kernel>=6.2<6.6.23
Linux Linux kernel>=6.7<6.7.11
debian/linux
5.10.223-15.10.234-16.1.129-16.1.135-16.12.27-1
redhat/kernel<4.19.311
4.19.311
redhat/kernel<5.4.273
5.4.273
redhat/kernel<5.10.214
5.10.214
redhat/kernel<5.15.153
5.15.153
redhat/kernel<6.1.83
6.1.83
redhat/kernel<6.6.23
6.6.23
redhat/kernel<6.7.11
6.7.11
redhat/kernel<6.8
6.8
Microsoft azl3 kernel 6.6.22.1-2
Microsoft azl3 kernel 6.6.29.1-3

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. 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.27-1
  2. Upgrade

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

    Fixed in 4.19.311
  3. Upgrade

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

    Fixed in 5.4.273
  4. Upgrade

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

    Fixed in 5.10.214
  5. Upgrade

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

    Fixed in 5.15.153
  6. Upgrade

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

    Fixed in 6.1.83
  7. Upgrade

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

    Fixed in 6.6.23
  8. Upgrade

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

    Fixed in 6.7.11
  9. Upgrade

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

    Fixed in 6.8
  10. Compensating control

    In rfcomm_process_rx, check whether sk->sk_state is BT_CLOSED before calling rfcomm_recv_frame.

Event History

Apr 17, 2024
CVE Published
via MITRE·10:27 AM
Data Sourced
via MITRE·10:27 AM
Description
Data Sourced
via NVD·11:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·05:33 PM
DescriptionSeverityAffected Software
Jun 8, 2024
Data Sourced
via Launchpad·01:10 AM
Description
Jun 30, 2024
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Apr 28, 2025
Data Sourced
via Ubuntu·02:21 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-26903?

CVE-2024-26903 is classified as a high severity vulnerability in the Linux kernel affecting Bluetooth RFCOMM.

2

How do I fix CVE-2024-26903?

To fix CVE-2024-26903, update your Linux kernel to versions 4.19.311, 5.4.273, 5.10.214, 5.15.153, 6.1.83, 6.6.23, 6.7.11, or 6.8 as applicable.

3

What systems are affected by CVE-2024-26903?

CVE-2024-26903 affects various versions of the Linux kernel across distributions such as Red Hat and Debian.

4

What component of Linux is impacted by CVE-2024-26903?

CVE-2024-26903 impacts the Bluetooth RFCOMM layer in the Linux kernel.

5

Is CVE-2024-26903 being actively exploited?

There is no current evidence of active exploitation for CVE-2024-26903, but users are encouraged to apply updates promptly.

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