CVE-2026-98107
CVE CVE-2026-98107EUVD EUVD-2026-86938Published 2026-09-25T10:35:56.000Z
What the advisory describes
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.
Source: EUVD (ENISA), in the words of the advisory.
Products the advisory names
These come from the advisory itself, not from any check we performed.
- Linux — Linux da49b602f7f75ccc91386e1274b3ef71676cd092 <ce0927eb3ee2939fab5ce3f9334bfd2fafb38481; da49b602f7f75ccc91386e1274b3ef71676cd092 <6da5c0331fc3ef0c7b8df8269523fc3b2cce1e65; da49b602f7f75ccc91386e1274b3ef71676cd092 <56c2b5831d39dc84aad2573dc3e197af1a872a05; patch: 6.12.111; patch: 6.18.53; 5.7; patch: 7.2.7; patch: 0; patch: 7.3-rc2; da49b602f7f75ccc91386e1274b3ef71676cd092 <df8c3af6132640da4788e96a02d653e642059803
The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.
Carried in the product catalogue
An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.
- Linux — Linux
Does this concern one of your customers?
This page cannot answer that — it does not know your estate. Whoever has recorded their environments gets the answer the morning after publication, together with a paragraph they can forward to the customer unedited.
Try it for 28 daysPatchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.