Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
  • Support the projectPage
Back

CVE-2026-53124

ublk: reset per-IO canceled flag on each fetch

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).

Timeline

  1. ID reserved

    By Linux

  2. · 15 days later

    Published

  3. · 4 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-53124, by who scored it
Scored byCVSSScoreVector
NVDNVD · Modified3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.16% · top 95% of all CVEs (10 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b – < de05e37d02f3f33ebca4967164e54f5fea809d86
    • affected 728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b – < 63335e5a67d89bb7cb9b023bbb3785896587a648
    • affected 728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b – < 0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b
    • affected 42ea64e01c96e594fb4f80c54dfe4f934d008a6e
    • affected 6.14.6 – < 6.15
  • Linux · Linux

    • affected 6.15
    • unaffected < 6.15
    • unaffected 6.18.57 – ≤ 6.18.*
    • unaffected 7.0.10 – ≤ 7.0.*
    • unaffected 7.1 – ≤ *

References

3

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-53124 badge
[![CVE-2026-53124](https://cveledger.app/badge/CVE-2026-53124.svg)](https://cveledger.app/cve/CVE-2026-53124)

Record last updated .