In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers… (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.
AI Analysis
Technical Summary
The vulnerability in the Linux kernel's Samsung serial driver involves redundant acquisition of the port->lock spinlock in the rx helper functions s3c24xx_serial_rx_enable() and s3c24xx_serial_rx_disable(). When console flow control (UPF_CONS_FLOW) is enabled, the serial core calls stop_tx() and start_tx() callbacks with the port->lock already held. Internally, stop_tx() is called with the lock held as well. However, the rx helper functions attempt to acquire the same spinlock again unconditionally, causing a deadlock since spinlocks are not recursive. The fix removes the redundant lock acquisition from these helper functions to resolve the deadlock.
Potential Impact
The vulnerability causes a deadlock on the same CPU when console flow control is enabled in the Samsung serial driver, potentially leading to system hangs or unresponsiveness in affected environments using this driver. There is no indication of code execution or privilege escalation from the provided data.
Mitigation Recommendations
A fix has been applied to the Linux kernel to remove the redundant port lock acquisition in the Samsung serial driver's rx helper functions. Users should update to a kernel version that includes this fix. Since this is a kernel-level issue, applying the official kernel update or patch from the Linux kernel maintainers is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should verify with the vendor or kernel release notes for the exact fixed version.
In the Linux kernel, the following vulnerability has been resolved: tty: serial: samsung: Remove redundant port lock acquisition in rx helpers… (CVE-2026-64528)
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.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in the Linux kernel's Samsung serial driver involves redundant acquisition of the port->lock spinlock in the rx helper functions s3c24xx_serial_rx_enable() and s3c24xx_serial_rx_disable(). When console flow control (UPF_CONS_FLOW) is enabled, the serial core calls stop_tx() and start_tx() callbacks with the port->lock already held. Internally, stop_tx() is called with the lock held as well. However, the rx helper functions attempt to acquire the same spinlock again unconditionally, causing a deadlock since spinlocks are not recursive. The fix removes the redundant lock acquisition from these helper functions to resolve the deadlock.
Potential Impact
The vulnerability causes a deadlock on the same CPU when console flow control is enabled in the Samsung serial driver, potentially leading to system hangs or unresponsiveness in affected environments using this driver. There is no indication of code execution or privilege escalation from the provided data.
Mitigation Recommendations
A fix has been applied to the Linux kernel to remove the redundant port lock acquisition in the Samsung serial driver's rx helper functions. Users should update to a kernel version that includes this fix. Since this is a kernel-level issue, applying the official kernel update or patch from the Linux kernel maintainers is the recommended remediation. Patch status is not explicitly confirmed in the provided data; users should verify with the vendor or kernel release notes for the exact fixed version.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-9gfg-cjvv-9789
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-64528"]
- Ecosystems
- []
- Database Specific Severity
- null
- Cvss Version
- null
Threat ID: 6a6542059c2644c7f8081ae7
Added to database: 07/25/2026, 23:08:53 UTC
Last enriched: 07/25/2026, 23:12:00 UTC
Last updated: 09/07/2026, 15:46:57 UTC
Views: 41
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.