CVE-2026-64528

UNRATEDCVSS · not yet scoredTrending — 3 sources updated this week
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS v2: Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

tty: serial: samsung: Remove redundant port lock acquisition in rx helpers

Sashiko identified a deadlock when the console flow is engaged [1].

When console flow control is enabled (UPF_CONS_FLOW), s3c24xx_serial_stop_tx() calls s3c24xx_serial_rx_enable() and s3c24xx_serial_start_tx() calls s3c24xx_serial_rx_disable().

The serial core framework invokes the .stop_tx() and .start_tx() callbacks with the port->lock spinlock already held. Furthermore, all internal driver paths that invoke stop_tx (such as the DMA TX completion handler s3c24xx_serial_tx_dma_complete() or the PIO TX IRQ handler s3c24xx_serial_tx_irq()) also acquire port->lock prior to calling it. (Note that s3c24xx_serial_start_tx() is only invoked by the serial core).

However, s3c24xx_serial_rx_enable() and s3c24xx_serial_rx_disable() unconditionally attempt to acquire port->lock again using uart_port_lock_irqsave(). Since spinlocks are not recursive, this causes a deadlock on the same CPU when console flow control is engaged.

Remove the redundant lock acquisition from both rx helper functions.

CVSS v3
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
EG Risk
EPSS PROB
0%
EPSS %ILE
6%
KEV
Not listed

Published

July 25, 2026

Last Modified

July 25, 2026

Vendor Advisories for CVE-2026-64528(1)

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

Patch Availability(4)

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
linux5.10.103-1 ... 5.10.92-2 (54 versions)5.10.259-1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (141 versions)7.0.12-1

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 6× in last 7d / 35× 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-09-13 21:22 UTCVendor advisory
  2. 2026-09-13 21:22 UTCGHSA enrichment
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-10 20:51 UTCVendor advisory
  6. 2026-09-10 20:51 UTCGHSA enrichment
  7. 2026-09-08 22:01 UTCEPSS rescore
  8. 2026-09-07 21:09 UTCGHSA enrichment
  9. 2026-09-07 16:01 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-05 15:31 UTCEPSS rescore
  12. 2026-09-04 12:37 UTCGHSA enrichment
  13. 2026-09-04 05:07 UTCEPSS rescore
  14. 2026-09-02 14:12 UTCEPSS rescore
  15. 2026-09-01 13:54 UTCEPSS rescore
  16. 2026-09-01 04:40 UTCEPSS rescore
  17. 2026-08-30 19:54 UTCVendor advisory
  18. 2026-08-30 19:53 UTCGHSA enrichment
  19. 2026-08-30 19:17 UTCEPSS rescore
  20. 2026-08-28 21:42 UTCEPSS rescore
  21. 2026-08-27 21:04 UTCVendor advisory
  22. 2026-08-27 21:04 UTCGHSA enrichment
  23. 2026-08-26 14:47 UTCEPSS rescore
  24. 2026-08-25 13:49 UTCEPSS rescore
  25. 2026-08-24 18:00 UTCVendor advisory
Show 52 more
  1. 2026-08-24 18:00 UTCGHSA enrichment
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 17:39 UTCVendor advisory
  4. 2026-08-21 17:39 UTCGHSA enrichment
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:04 UTCEPSS rescore
  7. 2026-08-18 18:49 UTCVendor advisory
  8. 2026-08-18 18:49 UTCGHSA enrichment
  9. 2026-08-18 13:48 UTCEPSS rescore
  10. 2026-08-17 13:47 UTCEPSS rescore
  11. 2026-08-16 14:56 UTCEPSS rescore
  12. 2026-08-15 18:33 UTCVendor advisory
  13. 2026-08-15 18:33 UTCGHSA enrichment
  14. 2026-08-15 01:30 UTCEPSS rescore
  15. 2026-08-12 19:43 UTCVendor advisory
  16. 2026-08-12 19:43 UTCGHSA enrichment
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-11 00:00 UTCEPSS rescore
  19. 2026-08-09 20:54 UTCVendor advisory
  20. 2026-08-09 20:54 UTCGHSA enrichment
  21. 2026-08-09 13:47 UTCEPSS rescore
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-06 22:04 UTCVendor advisory
  24. 2026-08-06 22:04 UTCGHSA enrichment
  25. 2026-08-06 13:47 UTCEPSS rescore
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 19:17 UTCEPSS rescore
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 10:39 UTCEPSS rescore
  30. 2026-08-03 23:15 UTCVendor advisory
  31. 2026-08-03 23:15 UTCGHSA enrichment
  32. 2026-08-03 10:36 UTCEPSS rescore
  33. 2026-08-02 02:27 UTCEPSS rescore
  34. 2026-08-01 04:16 UTCEPSS rescore
  35. 2026-08-01 00:25 UTCEG score recompute
  36. 2026-08-01 00:25 UTCGHSA enrichment
  37. 2026-07-30 16:28 UTCEPSS rescore
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-30 01:30 UTCEPSS rescore
  40. 2026-07-29 01:35 UTCEG score recompute
  41. 2026-07-29 01:35 UTCGHSA enrichment
  42. 2026-07-28 15:37 UTCEPSS rescore
  43. 2026-07-27 14:14 UTCEPSS rescore
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-26 02:45 UTCEG score recompute
  47. 2026-07-26 02:45 UTCGHSA enrichment
  48. 2026-07-25 14:18 UTCEPSS rescore
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-25 10:39 UTCNVD update
  51. 2026-07-25 10:02 UTCEG score recompute
  52. 2026-07-25 10:01 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-64528?
CVE-2026-64528 is a publicly disclosed vulnerability published on July 25, 2026. In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers Sashiko identified a deadlock when the console flow is engaged [1]. When console flow control is enabled (UPFCONSFLOW), s3c24xxserialstoptx() calls…
When was CVE-2026-64528 disclosed?
CVE-2026-64528 was first published in the National Vulnerability Database on July 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64528 actively exploited?
CVE-2026-64528 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 93.6% of all scored CVEs.
How do I remediate CVE-2026-64528?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64528, 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-64528

Explore →

Is Your Infrastructure Affected by CVE-2026-64528?

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