CVE-2026-53384

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM 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: 1%CVSS: 9.8Exploit: None knownExposed: 0

A fix is available — apply it.

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(medium)
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%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
42%
KEV
Not listed

Published

July 19, 2026

Last Modified

August 17, 2026

Advisory Details (7)

Auto-updated Sep 7, 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.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-31.31) @ resolute2026-09-07ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1013.13) @ resolute2026-09-07ubuntu
ubuntulinux-tools-gcp-edge (7.0.0-1011.11~24.04.1) @ noble2026-09-07ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
linux-6.16.1.106-3~deb11u1 ... 6.1.176-1~deb11u1 (21 versions)6.1.177-1~deb11u1—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (54 versions)6.1.177-1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.95-1~bpo12+1 (29 versions)6.12.95-1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (146 versions)7.0.14-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(3)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 20× in last 7d / 224× 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.

Showing the most recent 100 of 382 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 23:47 UTCEG score recompute
  5. 2026-09-07 23:47 UTCVendor advisory
  6. 2026-09-07 23:47 UTCGHSA enrichment
  7. 2026-09-07 16:01 UTCEPSS rescore
  8. 2026-09-06 17:35 UTCEG score recompute
  9. 2026-09-06 17:35 UTCVendor advisory
  10. 2026-09-06 17:35 UTCGHSA enrichment
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-06 13:18 UTCVendor advisory
  13. 2026-09-06 13:18 UTCGHSA enrichment
  14. 2026-09-06 04:29 UTCVendor advisory
  15. 2026-09-06 04:29 UTCGHSA enrichment
  16. 2026-09-06 00:29 UTCVendor advisory
  17. 2026-09-06 00:29 UTCGHSA enrichment
  18. 2026-09-05 20:21 UTCEG score recompute
  19. 2026-09-05 20:21 UTCVendor advisory
  20. 2026-09-05 20:21 UTCGHSA enrichment
  21. 2026-09-04 05:06 UTCEPSS rescore
  22. 2026-09-02 14:12 UTCEPSS rescore
  23. 2026-09-01 13:54 UTCEPSS rescore
  24. 2026-09-01 04:40 UTCEPSS rescore
  25. 2026-08-31 03:32 UTCVendor advisory
Show 75 more
  1. 2026-08-31 03:32 UTCGHSA enrichment
  2. 2026-08-30 23:36 UTCVendor advisory
  3. 2026-08-30 23:36 UTCGHSA enrichment
  4. 2026-08-30 19:41 UTCEG score recompute
  5. 2026-08-30 19:41 UTCVendor advisory
  6. 2026-08-30 19:41 UTCGHSA enrichment
  7. 2026-08-30 19:17 UTCEPSS rescore
  8. 2026-08-30 15:45 UTCVendor advisory
  9. 2026-08-30 15:45 UTCGHSA enrichment
  10. 2026-08-30 10:58 UTCVendor advisory
  11. 2026-08-30 10:58 UTCGHSA enrichment
  12. 2026-08-30 07:03 UTCVendor advisory
  13. 2026-08-30 07:02 UTCGHSA enrichment
  14. 2026-08-30 03:05 UTCEG score recompute
  15. 2026-08-30 03:05 UTCVendor advisory
  16. 2026-08-30 03:05 UTCGHSA enrichment
  17. 2026-08-30 01:22 UTCEPSS rescore
  18. 2026-08-28 21:41 UTCEPSS rescore
  19. 2026-08-28 01:46 UTCVendor advisory
  20. 2026-08-28 01:46 UTCGHSA enrichment
  21. 2026-08-27 21:25 UTCEG score recompute
  22. 2026-08-27 21:25 UTCVendor advisory
  23. 2026-08-27 21:25 UTCGHSA enrichment
  24. 2026-08-27 14:25 UTCEPSS rescore
  25. 2026-08-27 12:00 UTCVendor advisory
  26. 2026-08-27 12:00 UTCGHSA enrichment
  27. 2026-08-27 02:25 UTCVendor advisory
  28. 2026-08-27 02:25 UTCGHSA enrichment
  29. 2026-08-26 22:30 UTCEG score recompute
  30. 2026-08-26 22:30 UTCVendor advisory
  31. 2026-08-26 22:30 UTCGHSA enrichment
  32. 2026-08-26 14:46 UTCEPSS rescore
  33. 2026-08-26 12:56 UTCVendor advisory
  34. 2026-08-26 12:56 UTCGHSA enrichment
  35. 2026-08-26 09:00 UTCVendor advisory
  36. 2026-08-26 09:00 UTCGHSA enrichment
  37. 2026-08-26 04:49 UTCVendor advisory
  38. 2026-08-26 04:49 UTCGHSA enrichment
  39. 2026-08-26 00:53 UTCVendor advisory
  40. 2026-08-26 00:53 UTCGHSA enrichment
  41. 2026-08-25 20:21 UTCVendor advisory
  42. 2026-08-25 20:21 UTCGHSA enrichment
  43. 2026-08-25 15:42 UTCEG score recompute
  44. 2026-08-25 15:42 UTCVendor advisory
  45. 2026-08-25 15:42 UTCGHSA enrichment
  46. 2026-08-25 13:49 UTCEPSS rescore
  47. 2026-08-25 11:31 UTCVendor advisory
  48. 2026-08-25 11:31 UTCGHSA enrichment
  49. 2026-08-25 07:36 UTCVendor advisory
  50. 2026-08-25 07:36 UTCGHSA enrichment
  51. 2026-08-25 03:40 UTCGHSA enrichment
  52. 2026-08-24 23:44 UTCVendor advisory
  53. 2026-08-24 23:44 UTCGHSA enrichment
  54. 2026-08-24 19:49 UTCVendor advisory
  55. 2026-08-24 19:49 UTCGHSA enrichment
  56. 2026-08-24 15:53 UTCEG score recompute
  57. 2026-08-24 15:53 UTCVendor advisory
  58. 2026-08-24 15:53 UTCGHSA enrichment
  59. 2026-08-24 11:46 UTCEG score recompute
  60. 2026-08-24 11:46 UTCVendor advisory
  61. 2026-08-24 11:45 UTCGHSA enrichment
  62. 2026-08-24 07:49 UTCVendor advisory
  63. 2026-08-24 07:49 UTCGHSA enrichment
  64. 2026-08-24 03:44 UTCVendor advisory
  65. 2026-08-24 03:44 UTCGHSA enrichment
  66. 2026-08-23 23:03 UTCVendor advisory
  67. 2026-08-23 23:03 UTCGHSA enrichment
  68. 2026-08-23 18:57 UTCVendor advisory
  69. 2026-08-23 18:57 UTCGHSA enrichment
  70. 2026-08-23 15:01 UTCVendor advisory
  71. 2026-08-23 15:01 UTCGHSA enrichment
  72. 2026-08-23 11:05 UTCVendor advisory
  73. 2026-08-23 11:05 UTCGHSA enrichment
  74. 2026-08-23 07:09 UTCVendor advisory
  75. 2026-08-23 07:09 UTCGHSA enrichment

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 August 17, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 57.7% 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

See which npm, PyPI, Go, and Maven packages are affected by 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.

Start Free Scan →Browse All CVEs