CVE-2026-53124
Last modified
CVE-2026-53124 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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).
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.14.6, < 6.15 |
| Linux | Linux Kernel | >= 6.15.1, < 7.0.10 |
| Linux | Linux Kernel | 6.15 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-53124?
How severe is CVE-2026-53124?
How do I fix CVE-2026-53124?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-53119In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5312A weakness has been identified in D-Link DNS-120, DNR-202L, …5.5
- CVE-2026-53120In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-53121In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53122In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53123In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53125In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53126In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53127In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53128In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-53129In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-5313A vulnerability has been found in Nothings stb up to 2.30. T…4.3
Are you affected by CVE-2026-53124?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
