Threats Tagged 'cve-2026-53124'
View all threats tagged with 'cve-2026-53124'. Filter and sort to focus on specific types of threats.
Stop chasing alerts. Route them.
Start free, then upgrade once to turn Radar into an automated delivery engine for your security stack.
Custom feeds / Automations: email, Slack, webhooks, SIEM/MISP / API access (baseline limits)
API access activates after upgrading in Console -> Billing.
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.
Filter Threats
Narrow down the results by type, severity, or affected countries
Threats Tagged 'cve-2026-53124'
Click on any threat for detailed analysis and mitigation recommendations
A vulnerability in the Linux kernel's ublk subsystem involves improper resetting of per-IO canceled flags during IO fetch operations. If a ublk server crashes before fetching all IOs, some fetch commands may never be properly canceled, causing outstanding commands to remain uncompleted. This issue has been fixed by resetting the per-IO canceled flags immediately upon each IO fetch rather than waiting for all IOs in a queue to be fetched. Join the discussion | GCVE Database | 06/24/2026, 18:32:48 UTC Added: 07/23/2026, 22:51:59 UTC |
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). Join the discussion | GCVE Database | 06/24/2026, 17:17:00 UTC Added: 07/17/2026, 10:17:04 UTC |
Showing 1 to 2 of 2 results