Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-53073

5.5 · MEDIUM

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_PROT…

Published Jun 24, 2026CWE-476EPSS 0.11%

Overview

CVE-2026-53073 is a medium-severity vulnerability. It was published on June 24, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

References

Refgit.kernel.org/stable/c/194f029a4d7f739e44ebc1f473120187b4de5104Refgit.kernel.org/stable/c/356dee1bcac4d0d9152390561fa63331ebff211bRefgit.kernel.org/stable/c/3daa5818e473ed60eb69d8b5c71b651909d28c5aRefgit.kernel.org/stable/c/68d39ea5e0adc9ecaea1ce8abd842ec972eb8718Refgit.kernel.org/stable/c/a673cf6c4ac702cb79ac1f4d7fc4de763a6a3e40Refgit.kernel.org/stable/c/ebb39b2d81731b83ee71a1ba6dd0291a57b5ac07Refgit.kernel.org/stable/c/ed4033fb85ccaaf6c3983be3c7b037e48253d232Refgit.kernel.org/stable/c/f4b69c35813c432973d340d3600c01de106ed474

How CyberStrike helps

Frequently asked questions

What is CVE-2026-53073?

CVE-2026-53073 is a medium-severity vulnerability. It was published on June 24, 2026 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2026-53073?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-53073?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-53073?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-53073 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999