CVE-2026-31510: Bluetooth: L2CAP: Fix null-ptr-deref on l2cap_sock_ready_cb

Published Apr 22, 2026
·
Updated

Bluetooth: L2CAP: Fix null-ptr-deref on l2capsockreadycb

Affected Software

18 affected componentsFixes available
Linux Linux kernel
Linux Linux kernel>=3.6.1<5.10.253
Linux Linux kernel>=5.11<5.15.203
Linux Linux kernel>=5.16<6.1.168
Linux Linux kernel>=6.2<6.6.131
Linux Linux kernel>=6.7<6.12.80
Linux Linux kernel>=6.13<6.18.21
Linux Linux kernel>=6.19<6.19.11
Linux Linux kernel=3.6
Linux Linux kernel=7.0-rc1
Linux Linux kernel=7.0-rc2
Linux Linux kernel=7.0-rc3
Linux Linux kernel=7.0-rc4
Linux Linux kernel=7.0-rc5
Linux Linux kernel=7.0-rc6
Linux Linux kernel=7.0-rc7
Microsoft azl3 kernel 6.6.130.1-3
Microsoft azl3 kernel 6.6.130.1-3<6.6.134.1-2
6.6.134.1-2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.6.134.1-2
  2. Compensating control

    In Bluetooth L2CAP l2cap_sock_ready_cb, check whether the sk pointer is null before using it.

Event History

Apr 22, 2026
CVE Published
via MITRE·01:54 PM
Data Sourced
via MITRE·01:54 PM
Description
Data Sourced
via NVD·02:16 PM
RemedyDescriptionSeverityWeaknessAffected Software
Apr 23, 2026
Data Sourced
via Microsoft·08:06 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:06 AM
DescriptionSeverity

Frequently Asked Questions

1

What is the severity of CVE-2026-31510?

CVE-2026-31510 has been classified as a medium severity vulnerability due to potential denial-of-service risks.

2

How do I fix CVE-2026-31510?

To resolve CVE-2026-31510, update the Linux kernel to the latest version that contains the patch.

3

What are the potential impacts of CVE-2026-31510?

CVE-2026-31510 could lead to a null pointer dereference, causing system instability or crashes.

4

Which versions of the Linux kernel are affected by CVE-2026-31510?

CVE-2026-31510 affects specific versions of the Linux kernel prior to the implementation of the fix.

5

Is there a workaround for CVE-2026-31510?

There are no known workarounds for CVE-2026-31510, and applying the patch is recommended.

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