CVE-2026-23461
Last modified
CVE-2026-23461 is a high-severity vulnerability rated 8.8/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user After commit ab4eedb790ca ("Bluetooth: L2CAP: Fix corrupted list in hci_chan_del"), l2cap_conn_del() uses conn->lock to protect access to conn->users. However, l2cap_register_user() and l2cap_unregister_user() don't use conn->lock, creating a race condition where these functions can access conn->users and conn->hchan concurrently with l2cap_conn_del(). This can lead to use-after-free and list corruption bugs, as reported by syzbot. Fix this by changing l2cap_register_user() and l2cap_unregister_user() to use conn->lock instead of hci_dev_lock(), ensuring consistent locking for the l2cap_conn structure.. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
Description
In the Linux kernel, the following vulnerability has been resolved: Bluetooth: L2CAP: Fix use-after-free in l2cap_unregister_user After commit ab4eedb790ca ("Bluetooth: L2CAP: Fix corrupted list in hci_chan_del"), l2cap_conn_del() uses conn->lock to protect access to conn->users. However, l2cap_register_user() and l2cap_unregister_user() don't use conn->lock, creating a race condition where these functions can access conn->users and conn->hchan concurrently with l2cap_conn_del(). This can lead to use-after-free and list corruption bugs, as reported by syzbot. Fix this by changing l2cap_register_user() and l2cap_unregister_user() to use conn->lock instead of hci_dev_lock(), ensuring consistent locking for the l2cap_conn structure.
Metrics
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.6.84, < 6.6.130 | — |
| Linux | Linux Kernel | >= 6.12.20, < 6.12.78 | — |
| Linux | Linux Kernel | >= 6.13.8, < 6.14 | — |
| Linux | Linux Kernel | >= 6.14.1, < 6.18.20 | — |
| Linux | Linux Kernel | >= 6.19, < 6.19.10 | — |
| Linux | Linux Kernel | 6.14 | — |
| Linux | Linux Kernel | 7.0 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-23461?
How severe is CVE-2026-23461?
How do I fix CVE-2026-23461?
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-23456In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-23457In the Linux kernel, the following vulnerability has been re…8.6
- CVE-2026-23458In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23459In the Linux kernel, the following vulnerability has been re…8.2
- CVE-2026-2346Authorization bypass through User-Controlled key vulnerabili…9.8
- CVE-2026-23460In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23462In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-23463In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-23464In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23465In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-23466In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-23467In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-23461?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
