CVE-2026-64528
tty: serial: samsung: Remove redundant port lock acquisition in rx helpers
Description
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.
INFO
Published Date :
July 25, 2026, 10:17 a.m.
Last Modified :
July 25, 2026, 10:17 a.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Affected Products
The following products are affected by CVE-2026-64528
vulnerability.
Even if cvefeed.io is aware of the exact versions of the
products
that
are
affected, the information is not represented in the table below.
No affected product recoded yet
Solution
- Remove redundant port lock acquisition in rx helpers.
- Update the Linux kernel to a version with this fix.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-64528.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-64528 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-64528
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-64528 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-64528 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 25, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'b497549a035c2a81b71c7a27f2b00c8a16c09423', 'lessThan': 'ee9eb72be95490602c493db050c73d925c3a4d74', 'versionType': 'git'}, {'status': 'affected', 'version': 'b497549a035c2a81b71c7a27f2b00c8a16c09423', 'lessThan': '10014eb7eee351f7b587f8ac85830f0c9343cb9a', 'versionType': 'git'}, {'status': 'affected', 'version': 'b497549a035c2a81b71c7a27f2b00c8a16c09423', 'lessThan': 'f4c3e63fa8639aedf96fb200d9939945a9eed51e', 'versionType': 'git'}, {'status': 'affected', 'version': 'b497549a035c2a81b71c7a27f2b00c8a16c09423', 'lessThan': 'a9c22e0f93ba18322a6623ecdda2f0cd858ca350', 'versionType': 'git'}, {'status': 'affected', 'version': 'b497549a035c2a81b71c7a27f2b00c8a16c09423', 'lessThan': '14143ec10d69f42806b5d7b046f0fd1b835831ae', 'versionType': 'git'}, {'status': 'affected', 'version': 'b497549a035c2a81b71c7a27f2b00c8a16c09423', 'lessThan': '9fd48937046efc9abb89379d63ee9cc5c661d711', 'versionType': 'git'}, {'status': 'affected', 'version': 'b497549a035c2a81b71c7a27f2b00c8a16c09423', 'lessThan': '9c92b42207978559e32903c3098aaf5c5b5788b2', 'versionType': 'git'}, {'status': 'affected', 'version': 'b497549a035c2a81b71c7a27f2b00c8a16c09423', 'lessThan': 'a3bb136bff5e6a5e48cdd813246c9c4686feaaa9', 'versionType': 'git'}], 'programFiles': ['drivers/tty/serial/samsung_tty.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '2.6.27'}, {'status': 'unaffected', 'version': '0', 'lessThan': '2.6.27', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '5.10.259', 'versionType': 'semver', 'lessThanOrEqual': '5.10.*'}, {'status': 'unaffected', 'version': '5.15.210', 'versionType': 'semver', 'lessThanOrEqual': '5.15.*'}, {'status': 'unaffected', 'version': '6.1.176', 'versionType': 'semver', 'lessThanOrEqual': '6.1.*'}, {'status': 'unaffected', 'version': '6.6.143', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.93', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.35', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.12', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['drivers/tty/serial/samsung_tty.c'], 'defaultStatus': 'affected'}] Added Description 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. Added Reference https://git.kernel.org/stable/c/10014eb7eee351f7b587f8ac85830f0c9343cb9a Added Reference https://git.kernel.org/stable/c/14143ec10d69f42806b5d7b046f0fd1b835831ae Added Reference https://git.kernel.org/stable/c/9c92b42207978559e32903c3098aaf5c5b5788b2 Added Reference https://git.kernel.org/stable/c/9fd48937046efc9abb89379d63ee9cc5c661d711 Added Reference https://git.kernel.org/stable/c/a3bb136bff5e6a5e48cdd813246c9c4686feaaa9 Added Reference https://git.kernel.org/stable/c/a9c22e0f93ba18322a6623ecdda2f0cd858ca350 Added Reference https://git.kernel.org/stable/c/ee9eb72be95490602c493db050c73d925c3a4d74 Added Reference https://git.kernel.org/stable/c/f4c3e63fa8639aedf96fb200d9939945a9eed51e