CVE-2026-31512: Linux kernel · Bluetooth: L2CAP: Validate PDU length before reading SDU length in
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in e47315b84d0eb188772c3ff5cf073cdbdefca6b4 : update Linux kernel when convenient.
Data as of 5 Nov 2026, 22:18 UTC
Rated Medium 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 e47315b84d0eb188772c3ff5cf073cdbdefca6b4, cef09691cfb61f6c91cc27c3d69634f81c8ab949, c65bd945d1c08c3db756821b6bf9f1c4a77b29c6 +5
Exploitation evidence
Disclosed: evidence found.
CVE published 22 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
AI-suggested
A fix is available and has been applied in the Linux kernel. Users and administrators should update to a fixed kernel version that includes the patches identified by the commit hashes provided. No additional mitigation actions are indicated.
Description
A vulnerability in the Linux kernel Bluetooth L2CAP implementation was fixed by adding validation of the PDU length before reading the SDU length in the function l2cap_ecred_data_rcv(). The flaw involved reading two bytes from a buffer without verifying that the buffer contained sufficient data, potentially causing out-of-bounds reads.
References
- git.kernel.org/stable/c/cef09691cfb61f6c91cc27c3d69634f81c8ab949 (opens in a new tab)
- git.kernel.org/stable/c/3340be2bafdcc806f048273ea6d8e82a6597aa1b (opens in a new tab)
- git.kernel.org/stable/c/e47315b84d0eb188772c3ff5cf073cdbdefca6b4 (opens in a new tab)
- git.kernel.org/stable/c/477ad4976072056c348937e94f24583321938df4 (opens in a new tab)
- git.kernel.org/stable/c/40c7f7eea2f4d9cb0b3e924254c8c9053372168f (opens in a new tab)
- git.kernel.org/stable/c/8c96f3bd4ae0802db90630be8e9851827e9c9209 (opens in a new tab)
- git.kernel.org/stable/c/5ad981249be52f5e4e92e0e97b436b569071cb86 (opens in a new tab)
- git.kernel.org/stable/c/c65bd945d1c08c3db756821b6bf9f1c4a77b29c6 (opens in a new tab)