CVE Catalog

CVE-2026-98107

Unknown
Published: Translated: NVD NIST

Summary

In the Linux kernel, Bluetooth L2CAP's l2cap_chan_connect() checks the limit of pending ECRED channels, but only counts deferred channels. If 6 L2CAP sockets are connected at the same time in order DDDDND (D=deferred, N=non-deferred), the last can exceed the limit, causing an out-of-bounds write in the scid array and sending an invalid ECRED_CONN_REQ. The fix accounts for non-deferred pending channels in the counting and adds a WARN_ON_ONCE check.

Risk Assessment

Out-of-bounds write in the Bluetooth stack could lead to system crash or potential remote code execution.

Recommendation

Install the kernel patch to avoid out-of-bounds writes in L2CAP and ensure correct ECRED connection handling.

Other vulnerabilities in Linux kernel

See all
Original NVD description (English source)

In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect l2cap_chan_connect() tries to ensure there are no more than L2CAP_ECRED_CONN_SCID_MAX pending ECRED channels, so they fit in the same L2CAP_ECRED_CONN_REQ that l2cap_ecred_connect() constructs. However, the check only counts deferred channels. If 6 L2CAP sockets are connected at the same time in order DDDDND (D=deferred, N=non-deferred), the last can bump the total to max+1. It results to one __le16 written out of bounds of the scid array, and an invalid ECRED_CONN_REQ being sent. Fix by leaving room for the non-deferred pending ECRED channels in the counting in l2cap_chan_connect(), so the limit can't be exceeded. Move counting under same critical section where the channel is added. Although race conditions involving this appear unreachable, it's easier to see. Also add WARN_ON_ONCE check in l2cap_ecred_defer_connect() to make this less brittle.

Vulnerability data from NVD (NIST) · CISA KEV · EPSS