CVE-2026-53384
Analyzed
Analyzed - Analysis Complete
Linux Kernel 8250 Port Use-After-Free
Vulnerability report for CVE-2026-53384, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.
Publication date: 2026-07-19
Last updated on: 2026-08-07
Assigner: kernel.org
Description
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 Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.2 (inc) to 6.6.144 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.95 (exc) |
| linux | linux_kernel | From 6.19 (inc) to 7.0.14 (exc) |
| linux | linux_kernel | From 7.1 (inc) to 7.1.2 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.38 (exc) |
| linux | linux_kernel | From 5.19 (inc) to 6.1.177 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |