Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64528tty: 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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Awaiting Analysis.

EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (15 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected b497549a035c2a81b71c7a27f2b00c8a16c09423 – < ee9eb72be95490602c493db050c73d925c3a4d74
    • affected b497549a035c2a81b71c7a27f2b00c8a16c09423 – < 10014eb7eee351f7b587f8ac85830f0c9343cb9a
    • affected b497549a035c2a81b71c7a27f2b00c8a16c09423 – < f4c3e63fa8639aedf96fb200d9939945a9eed51e
    • affected b497549a035c2a81b71c7a27f2b00c8a16c09423 – < a9c22e0f93ba18322a6623ecdda2f0cd858ca350
    • affected b497549a035c2a81b71c7a27f2b00c8a16c09423 – < 14143ec10d69f42806b5d7b046f0fd1b835831ae
    • affected b497549a035c2a81b71c7a27f2b00c8a16c09423 – < 9fd48937046efc9abb89379d63ee9cc5c661d711
    • affected b497549a035c2a81b71c7a27f2b00c8a16c09423 – < 9c92b42207978559e32903c3098aaf5c5b5788b2
    • affected b497549a035c2a81b71c7a27f2b00c8a16c09423 – < a3bb136bff5e6a5e48cdd813246c9c4686feaaa9
  • Linux · Linux

    • affected 2.6.27
    • unaffected < 2.6.27
    • unaffected 5.10.259 – ≤ 5.10.*
    • unaffected 5.15.210 – ≤ 5.15.*
    • unaffected 6.1.176 – ≤ 6.1.*
    • unaffected 6.6.143 – ≤ 6.6.*
    • unaffected 6.12.93 – ≤ 6.12.*
    • unaffected 6.18.35 – ≤ 6.18.*
    • unaffected 7.0.12 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64528 badge
[![CVE-2026-64528](https://cveledger.app/badge/CVE-2026-64528.svg)](https://cveledger.app/cve/CVE-2026-64528)

Record last updated .