In the Linux kernel, the following vulnerability has been resolved: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails… (CVE-2026-53384)
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.
AI Analysis
Technical Summary
In the Linux kernel serial driver 8250_dw, the dw8250_probe() function registers an 8250 port and then attempts to register a clock notifier if the device has a clock. If clk_notifier_register() fails, the probe function returns an error but does not unregister the previously registered 8250 port. The corresponding unregister function is only called during device removal, which does not occur on probe failure. As a result, the port slot remains occupied and references freed driver data, creating a use-after-free vulnerability. The fix involves unregistering the port if clk_notifier_register() fails to prevent stale references.
Potential Impact
The vulnerability can lead to use-after-free conditions where the kernel accesses freed memory via the stale 8250 port slot. This may cause system instability or crashes. There is no evidence of known exploits in the wild. The impact is limited to affected Linux kernel serial driver instances where the failure scenario occurs.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates the issue has been resolved in the Linux kernel source by unregistering the port on clk_notifier_register() failure. Users should monitor official Linux kernel advisories and apply updates when available.
In the Linux kernel, the following vulnerability has been resolved: serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails… (CVE-2026-53384)
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 v3.1
Score 9.8critical
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In the Linux kernel serial driver 8250_dw, the dw8250_probe() function registers an 8250 port and then attempts to register a clock notifier if the device has a clock. If clk_notifier_register() fails, the probe function returns an error but does not unregister the previously registered 8250 port. The corresponding unregister function is only called during device removal, which does not occur on probe failure. As a result, the port slot remains occupied and references freed driver data, creating a use-after-free vulnerability. The fix involves unregistering the port if clk_notifier_register() fails to prevent stale references.
Potential Impact
The vulnerability can lead to use-after-free conditions where the kernel accesses freed memory via the stale 8250 port slot. This may cause system instability or crashes. There is no evidence of known exploits in the wild. The impact is limited to affected Linux kernel serial driver instances where the failure scenario occurs.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. The vulnerability description indicates the issue has been resolved in the Linux kernel source by unregistering the port on clk_notifier_register() failure. Users should monitor official Linux kernel advisories and apply updates when available.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-8qr8-6qvc-c8x9
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-53384"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- 3.1
Threat ID: 6a5d27ad2a4a8d59891322a3
Added to database: 07/19/2026, 19:38:21 UTC
Last enriched: 07/19/2026, 20:24:01 UTC
Last updated: 09/02/2026, 10:52:10 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.