CVE-2026-53384: Linux Kernel use-after-free (CVSS 9.8)

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.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredNone

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

Linux Kernel≥ 5.19 < 6.1.177 · ≥ 6.13 < 6.18.38 · ≥ 6.19 < 7.0.14 · ≥ 6.2 < 6.6.144

Remediation

Fixed in

Linux Kernel≥ 6.1.177

Patch & vendor advisories

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-53384 being actively exploited?

CVE-2026-53384 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.52%.

How severe is CVE-2026-53384?

CVE-2026-53384 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.52% probability of exploitation.

Which products are affected by CVE-2026-53384?

Affected products include Linux Kernel.

How do I fix CVE-2026-53384?

Upgrade affected software to a fixed version, for example Linux Kernel 6.1.177 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-53384 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo