CVE-2026-53073
Last modified
CVE-2026-53073 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. In the Linux kernel, the following vulnerability has been resolved: Bluetooth: hci_ldisc: Clear HCI_UART_PROTO_INIT on error When hci_register_dev() fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not cleared before calling hu->proto->close(hu) and setting hu->hdev to NULL. This means incoming UART data will reach the protocol-specific recv handler in hci_uart_tty_receive() after resources are freed. Clear HCI_UART_PROTO_INIT with a write lock before calling hu->proto->close() and setting hu->hdev to NULL. 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: hci_ldisc: Clear HCI_UART_PROTO_INIT on error When hci_register_dev() fails in hci_uart_register_dev() HCI_UART_PROTO_INIT is not cleared before calling hu->proto->close(hu) and setting hu->hdev to NULL. This means incoming UART data will reach the protocol-specific recv handler in hci_uart_tty_receive() after resources are freed. Clear HCI_UART_PROTO_INIT with a write lock before calling hu->proto->close() and setting hu->hdev to NULL. The write lock ensures all active readers have completed and no new reader can enter the protocol recv path before resources are freed. This allows the protocol-specific recv functions to remove the "HCI_UART_REGISTERED" guard without risking a null pointer dereference if hci_register_dev() fails.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 5.4.293, < 5.5 |
| Linux | Linux Kernel | >= 5.10.237, < 5.10.258 |
| Linux | Linux Kernel | >= 5.15.181, < 5.15.209 |
| Linux | Linux Kernel | >= 6.1.135, < 6.1.175 |
| Linux | Linux Kernel | >= 6.6.88, < 6.6.141 |
| Linux | Linux Kernel | >= 6.12.24, < 6.12.91 |
| Linux | Linux Kernel | >= 6.13.12, < 6.14 |
| Linux | Linux Kernel | >= 6.14.3, < 6.18.33 |
| Linux | Linux Kernel | >= 6.19, < 7.0.10 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53073?
How severe is CVE-2026-53073?
How do I fix CVE-2026-53073?
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-53068In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53069In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-5307Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMB…
- CVE-2026-53070In the Linux kernel, the following vulnerability has been re…7.5
- CVE-2026-53071In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53072In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53074In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53075In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2026-53076In the Linux kernel, the following vulnerability has been re…7.1
- CVE-2026-53077In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53078In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53079In the Linux kernel, the following vulnerability has been re…5.5
Are you affected by CVE-2026-53073?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
