Go to homepageCyberStrike

Menu

Star on GitHub · 3.2k
Sign inDownload

CVE-2026-53384

9.8 · CRITICAL

In the Linux kernel, the following vulnerability has been resolved: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails dw8250_probe() registers the 8250 port via serial8250_re…

Published Jul 19, 2026CWE-416EPSS 0.52%

Overview

CVE-2026-53384 is a critical-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails

dw8250_probe() registers the 8250 port via serial8250_register_8250_port()

and then, if the device has a clock, registers a clock notifier. If

clk_notifier_register() fails, probe returns the error but leaves the

8250 port registered. The matching serial8250_unregister_port() lives

in dw8250_remove(), which is not called when probe fails, so the port

slot stays occupied until the device is rebound or the system is

rebooted. The devm-allocated driver data is freed while the port still

references it (via the saved private_data and serial_in/serial_out

callbacks), so any access to that port slot before a rebind is a

use-after-free hazard.

Unregister the port on the clk_notifier_register() error path.

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/07ffe414a708ae60551401cec5d727ed156b8cafRefgit.kernel.org/stable/c/10fc708b4de7f86002d2d735a2dbf3b5b7f65692Refgit.kernel.org/stable/c/3d205fe80f2181f0109150ad1fa06ee5bc046935Refgit.kernel.org/stable/c/511d2b92f8d20de04acafab676150d26fb5c67f4Refgit.kernel.org/stable/c/778b9dda4b24005a27bcd9c35c110bf8d7f259caRefgit.kernel.org/stable/c/ccdf4510a3873b14e5e348cdb038717996f09fdaRefgit.kernel.org/stable/c/d72650a4f334581b23a1892b888a4cb1be142f76

How CyberStrike helps

Frequently asked questions

What is CVE-2026-53384?

CVE-2026-53384 is a critical-severity vulnerability. It was published on July 19, 2026 and has a CVSS 3.1 base score of 9.8 (CRITICAL).

How severe is CVE-2026-53384?

This vulnerability has a CVSS 3.1 base score of 9.8, rated CRITICAL. It can be exploited remotely over the network. No authentication or special privileges are required for exploitation.

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

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-53384?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-53384 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 CRITICAL CVEs from 2026

View all
Browse by year2026202520242023202220212020201920182017201620152014201320122011201020092008200720062005200420032002200120001999