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-2025-21820tty: xilinx_uartps: split sysrq handling

Description

In the Linux kernel, the following vulnerability has been resolved: tty: xilinx_uartps: split sysrq handling lockdep detects the following circular locking dependency: CPU 0 CPU 1 ========================== ============================ cdns_uart_isr() printk() uart_port_lock(port) console_lock() cdns_uart_console_write() if (!port->sysrq) uart_port_lock(port) uart_handle_break() port->sysrq = ... uart_handle_sysrq_char() printk() console_lock() The fixed commit attempts to avoid this situation by only taking the port lock in cdns_uart_console_write if port->sysrq unset. However, if (as shown above) cdns_uart_console_write runs before port->sysrq is set, then it will try to take the port lock anyway. This may result in a deadlock. Fix this by splitting sysrq handling into two parts. We use the prepare helper under the port lock and defer handling until we release the lock.

Timeline

  1. ID reserved

    By Linux

  2. · 2 months later

    Published

  3. · 15 months later

    Record updated

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

CVSS scores of CVE-2025-21820, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.17% · top 94% of all CVEs (18 Nov 2026)
Loading the EPSS history…

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

Affected products

  • Linux · Linux

    • affected 74ea66d4ca061a3cd4c0e924e51b60e924644852 – < e22a97700901ba5e8bf8db68056a0d50f9440cae
    • affected 74ea66d4ca061a3cd4c0e924e51b60e924644852 – < de5bd24197bd9ee37ec1e379a3d882bbd15c5065
    • affected 74ea66d4ca061a3cd4c0e924e51b60e924644852 – < 8ea0e7b3d7b8f2f0fc9db491ff22a0abe120801c
    • affected 74ea66d4ca061a3cd4c0e924e51b60e924644852 – < 9b88a7c4584ba67267a051069b8abe44fc9595b2
    • affected 74ea66d4ca061a3cd4c0e924e51b60e924644852 – < 4410dba9807a17a93f649a9f5870ceaf30a675a3
    • affected 74ea66d4ca061a3cd4c0e924e51b60e924644852 – < b06f388994500297bb91be60ffaf6825ecfd2afe
  • Linux · Linux

    • affected 4.6
    • unaffected < 4.6
    • unaffected 5.15.179 – ≤ 5.15.*
    • unaffected 6.1.129 – ≤ 6.1.*
    • unaffected 6.6.78 – ≤ 6.6.*
    • unaffected 6.12.14 – ≤ 6.12.*
    • unaffected 6.13.3 – ≤ 6.13.*
    • unaffected 6.14 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .