CVE-2026-98107
Last modified
CVE-2026-98107 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 5.7, < 6.6.160 | — |
| Linux | Linux Kernel | >= 6.7, < 6.12.111 | — |
| Linux | Linux Kernel | >= 6.13, < 6.18.53 | — |
| Linux | Linux Kernel | >= 6.19, < 7.2.7 | — |
| Linux | Linux Kernel | 7.3 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-98107?
How severe is CVE-2026-98107?
How do I fix CVE-2026-98107?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98101In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98102In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98103In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98104In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98105In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98106In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-98108In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-98109In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-9811A stored Cross-Site Scripting (XSS) vulnerability exists in …5.4
- CVE-2026-98110In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-98111In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-98112In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2026-98107?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
