← All Advisories
Reported from OT-Advisories.com as of

CVE-2026-31393

Last refreshed2026-10-17

Status: UPDATED  |  Advisory ID: CVE-2026-31393

Key Details

CVECVE-2026-31393
CVSS Score / Version
8.1 (High) / CVSS v3.1
Updated2026-10-16
CVSS Vector
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:H
CVSS Prose
attack vector is adjacent; attack complexity is low; privileges required is none; user interaction is none; scope is unchanged; confidentiality impact is high; integrity impact is none; availability impact is high.
Affected products
Linux Kernel
Classified as
CWE-125 (Out-of-bounds Read)

Affected Products, Subsystems & Sectors

VendorProductAffected VersionsPatch Status
LinuxLinux Kernel
SubsystemsOT Supporting Infrastructure
SectorsAll Sectors

What to Know

In the Linux kernel, the following vulnerability has been resolved:

Bluetooth: L2CAP: Validate L2CAP_INFO_RSP payload length before access

l2cap_information_rsp() checks that cmd_len covers the fixed

l2cap_info_rsp header (type + result, 4 bytes) but then reads

rsp->data without verifying that the payload is present:

- L2CAP_IT_FEAT_MASK calls get_unaligned_le32(rsp->data), which reads

4 bytes past the header (needs cmd_len >= 8).

- L2CAP_IT_FIXED_CHAN reads rsp->data[0], 1 byte past the header

(needs cmd_len >= 5).

A truncated L2CAP_INFO_RSP with result == L2CAP_IR_SUCCESS triggers an

out-of-bounds read of adjacent skb data.

Guard each data access with the required payload length check. If the

payload is too short, skip the read and let the state machine complete

with safe defaults (feat_mask and remote_fixed_chan remain zero from

kzalloc), so the info timer cleanup and l2cap_conn_start() still run

and the connection is not stalled. (NVD)

What to Do

Monitor Linux's web page for any future patch releases.

References

SourceReference
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2026-31393
CVEhttps://www.cve.org/CVERecord?id=CVE-2026-31393
Report compilation © 2026 OT-Advisories.com  ·  CC BY 4.0  ·  Source materials remain the property of their respective publishers as cited.