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-90209s390/debug: Fix deadlock during unregister

Description

In the Linux kernel, the following vulnerability has been resolved: s390/debug: Fix deadlock during unregister Unregistering an s390dbf debug area while one of the associated debugfs files is being written to can cause a deadlock: $ echo >.../vmur/level $ rmmod vmur =================================================== debugfs write debugfs_file_get() debug_unregister() mutex_lock(debug_mutex) debugfs_remove() wait for debugfs_file_put() debug_file_ops.write() debug_input() mutex_lock(debug_mutex) ==> DEADLOCK Fix this by splitting debug_unregister() into an s390dbf and debugfs part, and running only the s390dbf part with debug_mutex locked.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 32 days 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

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

EPSS (exploitation in 30 days)
0.21% · top 88% of all CVEs (16 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 9372a82892c2caa6bccab9a4081166fa769699f8 – < a214c3dacc779b2afcb0ac9c8001e45ee4ffb2ed
    • affected 9372a82892c2caa6bccab9a4081166fa769699f8 – < 183f8f6d64bb0510070c856b9927618c53014a7b
    • affected 9372a82892c2caa6bccab9a4081166fa769699f8 – < a08b70ed2d1ec907353a72f15163b8e34ff4b2f8
    • affected 9372a82892c2caa6bccab9a4081166fa769699f8 – < 45bb341d1b73eb293e0dd43d9b72bbc8b615d0ba
    • affected 9372a82892c2caa6bccab9a4081166fa769699f8 – < 5d83f3faa3fb7f23f298cfd40382611999de5d1d
    • affected 9372a82892c2caa6bccab9a4081166fa769699f8 – < 54e1259b75d6402a1d0cfb822b9bb2c507e53dab
    • affected 9372a82892c2caa6bccab9a4081166fa769699f8 – < 445c31ac638fd1af203d79bdf25fc0cb3149fbbc
    • affected c68ba4a708fbd0efdc384cd29250bb292a45e559
    • affected 86f9980909f31ab205323eeeb290fe3cbb4952b4
    • affected fe5793e90d3f572a87ba67fe2f0e1679fdff14f8
    • affected e234f66168f0d50c0d28154fb983a14e85c3c526
    • affected 5.4.146 – < 5.5
    • affected 5.10.65 – < 5.11
    • affected 5.13.17 – < 5.14
    • affected 5.14.4 – < 5.15
  • Linux · Linux

    • affected 5.15
    • unaffected < 5.15
    • unaffected 5.15.221 – ≤ 5.15.*
    • unaffected 6.1.188 – ≤ 6.1.*
    • unaffected 6.6.157 – ≤ 6.6.*
    • unaffected 6.12.110 – ≤ 6.12.*
    • unaffected 6.18.52 – ≤ 6.18.*
    • unaffected 7.2.6 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References7

Sources

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

Badge for a README or a ticket

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

Record last updated .