Skip to main content
VulnerabilityPublished Updated

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

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d34776c7fa1f2c510f1cdd14823aba701babb4ad : patch Linux kernel soon.

Data as of 5 Nov 2026, 22:18 UTC

Severity
High

Rated High by Threat Radar's AI analysis · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in d34776c7fa1f2c510f1cdd14823aba701babb4ad, b6552e0503973daf6f23bd6ed9273ef131ee364f, a04a760c06bb591989db659439efdf106f0bae76 +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 54a59aa2b562872781d6a8fc89f300d360941691, < d34776c7fa1f2c510f1cdd14823aba701babb4ad
Fixed in
  • d34776c7fa1f2c510f1cdd14823aba701babb4ad
LinuxLinuxAffected
  • ≥ 54a59aa2b562872781d6a8fc89f300d360941691, < b6552e0503973daf6f23bd6ed9273ef131ee364f
Fixed in
  • b6552e0503973daf6f23bd6ed9273ef131ee364f
LinuxLinuxAffected
  • ≥ 54a59aa2b562872781d6a8fc89f300d360941691, < a04a760c06bb591989db659439efdf106f0bae76
Fixed in
  • a04a760c06bb591989db659439efdf106f0bae76
LinuxLinuxAffected
  • ≥ 54a59aa2b562872781d6a8fc89f300d360941691, < 898b89c90ff9496e64b9331040778cc4e1b28c9d
Fixed in
  • 898b89c90ff9496e64b9331040778cc4e1b28c9d
LinuxLinuxAffected
  • ≥ 54a59aa2b562872781d6a8fc89f300d360941691, < 0780f9333852971ca77d110019e3a66ce5a7b100
Fixed in
  • 0780f9333852971ca77d110019e3a66ce5a7b100
LinuxLinuxAffected
  • ≥ 54a59aa2b562872781d6a8fc89f300d360941691, < 03d4eafb0f3788239df63575951f6b4c97bbfda4
Fixed in
  • 03d4eafb0f3788239df63575951f6b4c97bbfda4

AI-suggested

A fix is available and has been applied in multiple Linux kernel commits following version 3.6. Users and administrators should update their Linux kernel to a version that includes these fixes to mitigate the vulnerability.

Description

A null pointer dereference vulnerability in the Linux kernel's Bluetooth L2CAP component was fixed by adding a check for a null socket pointer before use. This flaw could cause a kernel panic due to a fatal exception. The issue was identified in version 3.6 and has been resolved in subsequent commits.

References

Community reviews

Loading reviews…