CVE-2026-53384

CRITICALPre-NVD 9.89.8
EchelonGraph scoreHIGH confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-19. a secondary CVSS source baseline 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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
9.8
EG Score
9.8(high)
EG Risk
49(Track)
EG Risk 49/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
39%
KEV
Not listed

Published

July 19, 2026

Last Modified

July 20, 2026

Advisory Details (7)

Auto-updated Jul 25, 2026
No patch confirmed yet.
generic

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/d72650a4f334581b23a1892b888a4cb1be142f76
generic

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/ccdf4510a3873b14e5e348cdb038717996f09fda
generic

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/778b9dda4b24005a27bcd9c35c110bf8d7f259ca
generic

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/511d2b92f8d20de04acafab676150d26fb5c67f4
generic

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/3d205fe80f2181f0109150ad1fa06ee5bc046935
generic

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/10fc708b4de7f86002d2d735a2dbf3b5b7f65692
generic

serial: 8250_dw: unregister 8250 port if clk_notifier_register() fails - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/07ffe414a708ae60551401cec5d727ed156b8caf

Vendor Advisories for CVE-2026-53384(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 21× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-27 07:00 UTCGHSA enrichment
  2. 2026-07-27 03:02 UTCGHSA enrichment
  3. 2026-07-26 23:03 UTCGHSA enrichment
  4. 2026-07-26 19:06 UTCGHSA enrichment
  5. 2026-07-26 15:09 UTCEG score recompute
  6. 2026-07-26 15:09 UTCGHSA enrichment
  7. 2026-07-26 14:54 UTCEPSS rescore
  8. 2026-07-26 11:12 UTCEG score recompute
  9. 2026-07-26 11:12 UTCGHSA enrichment
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:19 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-21 15:25 UTCEPSS rescore
  16. 2026-07-20 17:48 UTCEG score recompute
  17. 2026-07-20 17:48 UTCGHSA enrichment
  18. 2026-07-20 17:08 UTCEPSS rescore
  19. 2026-07-20 14:48 UTCEG score recompute 9.80
  20. 2026-07-20 14:48 UTCGHSA enrichment
  21. 2026-07-20 14:32 UTCMITRE cvelistV5CVSS v3 → 9.8 · severity → CRITICAL
  22. 2026-07-19 12:26 UTCNVD update
  23. 2026-07-19 12:15 UTCEG score recompute
  24. 2026-07-19 12:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-53384?
CVE-2026-53384 is a critical vulnerability published on July 19, 2026. In the Linux kernel, the following vulnerability has been resolved: serial: 8250dw: unregister 8250 port if clknotifier_register() fails dw8250probe() registers the 8250 port via serial8250register8250port() and then, if the device has a clock, registers a clock notifier. If clknotifierregister()…
When was CVE-2026-53384 disclosed?
CVE-2026-53384 was first published in the National Vulnerability Database on July 19, 2026, with the most recent update on July 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53384 actively exploited?
CVE-2026-53384 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 60.8% of all scored CVEs.
What is the CVSS score of CVE-2026-53384?
CVE-2026-53384 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-53384?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53384, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-53384

Explore →

Is Your Infrastructure Affected by CVE-2026-53384?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.