CVE-2026-31513High· 8.1▾ TwilightIn the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req Syzbot reported a KASAN stack-out-of-bounds read in l2cap_build_cmd() that is triggered by a mal…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 44.6 · likelihood 0.1 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.4%
Last analysed / modified upstream
In the Linux kernel, the following vulnerability has been resolved:
Bluetooth: L2CAP: Fix stack-out-of-bounds read in l2cap_ecred_conn_req
Syzbot reported a KASAN stack-out-of-bounds read in l2cap_build_cmd() that is triggered by a malformed Enhanced Credit Based Connection Request.
The vulnerability stems from l2cap_ecred_conn_req(). The function allocates
a local stack buffer (pdu) designed to hold a maximum of 5 Source Channel
IDs (SCIDs), totaling 18 bytes. When an attacker sends a request with more
than 5 SCIDs, the function calculates rsp_len based on this unvalidated
cmd_len before checking if the number of SCIDs exceeds
L2CAP_ECRED_MAX_CID.
If the SCID count is too high, the function correctly jumps to the
response label to reject the packet, but rsp_len retains the
attacker's oversized value. Consequently, l2cap_send_cmd() is instructed
to read past the end of the 18-byte pdu buffer, triggering a
KASAN panic.
Fix this by moving the assignment of rsp_len to after the num_scid
boundary check. If the packet is rejected, rsp_len will safely
remain 0, and the error response will only read the 8-byte base header
from the stack.
Linux >= 935f324e4b2461df2cf7f02b4195082b4304c708 < c8e1a27edb8b4e5afb56b384acd7b6c2dec1b7ccLinux >= e981a9392800ce2c5bca196a6ab2c55e9370efaa < 5b35f8211a913cfe7ab9d54fa36a272d2059a588Linux >= f3fdf2e7276a3edc5df55454275da20eac186970 < a3d9c50d69785ae02e153f000da1b5fd6dbfdf1bLinux >= c28d2bff70444a85b3b86aaf241ece9408c7858c < 9d87cb22195b2c67405f5485d525190747ad5493Linux >= 6.12.75 < 6.12.80Linux >= 6.18.16 < 6.18.21Linux >= 6.19.6 < 6.19.11Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets