CVE-2026-53124
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).
Affected versions
Linux kernel versions
6.14.6,
6.15
and later are affected. Fixed in
7.0.10,
7.1
and their respective stable series.
References
2 totalFrequently asked questions
-
What is CVE-2026-53124?
CVE-2026-53124 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.14.6 onward and has been patched in 7.0.10 and 7.1. CVE-2026-53124 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.
-
Is there a patch available for CVE-2026-53124?
Yes — CVE-2026-53124 has been patched. Fixed versions include 7.0.10 and 7.1. If you are running Linux kernel 6.14.6 or later up to the fix versions, apply the relevant patch for your kernel branch.
-
Is CVE-2026-53124 actively exploited?
No — CVE-2026-53124 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.