Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-64528Published 2026-07-25

CVE-2026-64528 — Linux

As of 2026-07-25, CVE-2026-64528 is a vulnerability in Linux, EPSS 0.1% (6.4th percentile). No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-64528 as of 2026-07-25; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS
—Not yet scored
EPSS
0.1%Higher than 6.4% of scored CVEs
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
0.3/10Threadlinqs triage score
Published
EPSS 0.1% (higher than 6.4% of all scored CVEs) · Priority 0.3/10 · Published 2026-07-25

Last updated:

What is CVE-2026-64528?

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.

1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 72 days ago.

Severity and exploitation probability

EPSS (FIRST)
0.1% probability of exploitation in the next 30 days, higher than 6.4% of all scored CVEs
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
0.3/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-07-25

Is CVE-2026-64528 being exploited?

It currently carries a trending score of 31 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-64528

No vendor patch reference has been recorded for CVE-2026-64528 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-64528

No threat campaign in the Threadlinqs corpus currently references CVE-2026-64528, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD, FIRST EPSS. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Other references

Showing 5 of 8 recorded references.