Skip to main content
Meet us at Black Hat USA 2026— Las Vegas, August 1–6Book a Meeting
Mallory
Medium

Out-of-bounds read in Linux kernel Bluetooth L2CAP l2cap_ecred_data_rcv()

IdentifiersCVE-2026-31512CWE-125

CVE-2026-31512 is a Linux kernel Bluetooth L2CAP flaw in the Enhanced Credit Based Flow Control data path. In l2cap_ecred_data_rcv(), the kernel reads the 2-byte SDU length field from skb->data via get_unaligned_le16() without first verifying that the socket buffer contains at least L2CAP_SDULEN_SIZE bytes. If skb->len is less than 2, the function reads past the valid end of the skb data, resulting in an out-of-bounds read. The issue was fixed by adding the same kind of length validation already used in the ERTM reassembly path, specifically ensuring sufficient data is present before reading the SDU length.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can trigger an out-of-bounds read in kernel Bluetooth processing, which may lead to a kernel crash or other availability impact in the affected Bluetooth stack. The supplied scoring context indicates adjacent-network attack potential and possible limited confidentiality impact, but the primary consequence described in the available material is denial of service through invalid memory access in kernel space.

Mitigation

If you can’t patch tonight, do this now.

Until patched kernels can be deployed, reduce exposure by disabling Bluetooth where not required, preventing untrusted or unnecessary Bluetooth connectivity, and limiting adjacent-device access to systems using Bluetooth L2CAP Enhanced Credit Based Flow Control. Because the vulnerable path is in kernel Bluetooth packet handling, minimizing Bluetooth attack surface is the most direct temporary mitigation.

Remediation

Patch, then assume compromise.

Apply a Linux kernel update that includes the fix for CVE-2026-31512. The remediation is to validate PDU length before reading the SDU length in l2cap_ecred_data_rcv(), analogous to the existing pskb_may_pull() check used in the ERTM reassembly path. SUSE indicates fixed packages are available across affected product lines, including for example SLES 15 SP6-LTSS kernel-default 6.4.0-150600.23.112.1 or later, SLES 15 SP7/SLED 15 SP7 kernel-default 6.4.0-150700.53.55.1 or later, and corresponding fixed kernel-rt builds where applicable.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
LinuxLinux Kerneloperating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.