CVE-2026-64528

CVE CVE-2026-64528EUVD EUVD-2026-49040Published 2026-07-25T09:20:51.000Z

What the advisory describes

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.

Source: EUVD (ENISA), in the words of the advisory.

Products the advisory names

These come from the advisory itself, not from any check we performed.

• Linux — Linux b497549a035c2a81b71c7a27f2b00c8a16c09423 <9c92b42207978559e32903c3098aaf5c5b5788b2; patch: 5.15.210; patch: 6.1.176; patch: 5.10.259; b497549a035c2a81b71c7a27f2b00c8a16c09423 <ee9eb72be95490602c493db050c73d925c3a4d74; b497549a035c2a81b71c7a27f2b00c8a16c09423 <14143ec10d69f42806b5d7b046f0fd1b835831ae; 2.6.27; patch: 7.0.12; b497549a035c2a81b71c7a27f2b00c8a16c09423 <10014eb7eee351f7b587f8ac85830f0c9343cb9a; b497549a035c2a81b71c7a27f2b00c8a16c09423 <a3bb136bff5e6a5e48cdd813246c9c4686feaaa9; patch: 6.6.143; patch: 6.18.35; b497549a035c2a81b71c7a27f2b00c8a16c09423 <9fd48937046efc9abb89379d63ee9cc5c661d711; b497549a035c2a81b71c7a27f2b00c8a16c09423 <a9c22e0f93ba18322a6623ecdda2f0cd858ca350; b497549a035c2a81b71c7a27f2b00c8a16c09423 <f4c3e63fa8639aedf96fb200d9939945a9eed51e; patch: 7.1; patch: 6.12.93; patch: 0

The versions shown are the advisory's own. Patchlage compares no version numbers and derives no judgement from them — which version is installed is something a person has to look up.

Carried in the product catalogue

An estate covering these products can be recorded in Patchlage. An advisory about them appears in the next morning's situation report.

• Linux — Linux

Patchlage reports hits and suspected hits. About everything else this system says nothing — neither this page nor the situation report ever claims that an estate is safe.