CVE-2026-98107

Bluetooth: L2CAP: fix out-of-bounds write in l2cap_ecred_connect

State
Published
Severity
Not scored
Published
Sep 25, 2026
Updated
Oct 21, 2026
Reserved
Sep 25, 2026

Read the record on cve.org

Description

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.

Scores

The record has no CVSS score.

Weaknesses

The record names no weakness.

Affected Products

ProductVersions
LinuxLinux
  • da49b602f7f75ccc91386e1274b3ef71676cd092 to before fabc5e04f123225daf980d03f2c5a05e7f0f0a7fAffected
  • da49b602f7f75ccc91386e1274b3ef71676cd092 to before ce0927eb3ee2939fab5ce3f9334bfd2fafb38481Affected
  • da49b602f7f75ccc91386e1274b3ef71676cd092 to before 6da5c0331fc3ef0c7b8df8269523fc3b2cce1e65Affected
  • da49b602f7f75ccc91386e1274b3ef71676cd092 to before df8c3af6132640da4788e96a02d653e642059803Affected
  • da49b602f7f75ccc91386e1274b3ef71676cd092 to before 56c2b5831d39dc84aad2573dc3e197af1a872a05Affected
LinuxLinux
  • 5.7Affected
  • before 5.7Not affected
  • 6.6.160 through 6.6.*Not affected
  • 6.12.111 through 6.12.*Not affected
  • 6.18.53 through 6.18.*Not affected
  • 7.2.7 through 7.2.*Not affected
  • 7.3 and laterNot affected

References

Every record here comes from the CVE Program’s CVE List. © 1999–2026 The MITRE Corporation. CVE is a registered trademark of The MITRE Corporation. The records are reproduced under the CVE Program terms of use.