CVE-2026-64528

published 25 Jul 2026 · updated 17 Nov 2026

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

5.5MediumCVSS 5.5EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 5.10.259, Kernel 5.15.210, Kernel 6.1.176 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=2.6.27 <5.10.259, >=5.11 <5.15.210, >=5.16 <6.1.176, >=6.13 <6.18.35, >=6.19 <7.0.12, >=6.2 <6.6.143, >=6.7 <6.12.93, =7.1, >=b497549a035c2a81b71c7a27f2b00c8a16c09423 <14143ec10d69f42806b5d7b046f0fd1b835831ae, >=b497549a035c2a81b71c7a27f2b00c8a16c09423 <9c92b42207978559e32903c3098aaf5c5b5788b2, >=b497549a035c2a81b71c7a27f2b00c8a16c09423 <9fd48937046efc9abb89379d63ee9cc5c661d711, >=b497549a035c2a81b71c7a27f2b00c8a16c09423 <a3bb136bff5e6a5e48cdd813246c9c4686feaaa9, >=b497549a035c2a81b71c7a27f2b00c8a16c09423 <a9c22e0f93ba18322a6623ecdda2f0cd858ca350, >=b497549a035c2a81b71c7a27f2b00c8a16c09423 <ee9eb72be95490602c493db050c73d925c3a4d74, >=b497549a035c2a81b71c7a27f2b00c8a16c09423 <f4c3e63fa8639aedf96fb200d9939945a9eed51e, =2.6.27, >=b497549a035c2a81b71c7a27f2b00c8a16c09423 <10014eb7eee351f7b587f8ac85830f0c9343cb9a5.10.259, 5.15.210, 6.1.176, 6.18.35, 7.0.12, 6.6.143, 6.12.93, 14143ec10d69f42806b5d7b046f0fd1b835831ae, 9c92b42207978559e32903c3098aaf5c5b5788b2, 9fd48937046efc9abb89379d63ee9cc5c661d711, a3bb136bff5e6a5e48cdd813246c9c4686feaaa9, a9c22e0f93ba18322a6623ecdda2f0cd858ca350, ee9eb72be95490602c493db050c73d925c3a4d74, f4c3e63fa8639aedf96fb200d9939945a9eed51e, 10014eb7eee351f7b587f8ac85830f0c9343cb9a
linux-kernel: Kernel>=2.6.27 <5.10.259, >=5.11.0 <5.15.210, >=5.16.0 <6.1.176, >=6.13.0 <6.18.35, >=6.19.0 <7.0.12, >=6.2.0 <6.6.143, >=6.7.0 <6.12.935.10.259, 5.15.210, 6.1.176, 6.18.35, 7.0.12, 6.6.143, 6.12.93

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-64528 severity on Zeptric[![CVE-2026-64528](https://zeptric.io/badge/cve/CVE-2026-64528.svg)](https://zeptric.io/cve/CVE-2026-64528)