Skip to content
Heist/ feed
Back to feed
UnratedFix available

ublk: reset per-IO canceled flag on each fetch

Type: advisorySources: OSV

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

Products
Kernel
Affected versions
Not specified
Fixed versions
6.18.57, 7.0.10
CVEs
CVE-2026-53124
Confirmed fixed CVEs
Not specified
Updated in this feed
3 Nov 2026, 07:00 UTC · Revision 1

Source evidence

ublk: reset per-IO canceled flag on each fetch

core-osv · Original source

Published 24 Jun 2026, 16:30 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).

osv:CVE-2026-53124

Kernel

Fixed versions: 6.18.57, 7.0.10

Complete source record
{
  "id": "349906c4f32834ef7d47988abe7f0395fd6cd2f9c4c315b5b5646edf83fdae2f",
  "url": "https://osv.dev/vulnerability/CVE-2026-53124",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "ublk: reset per-IO canceled flag on each fetch",
    "summary": "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).",
    "evidence": "osv:CVE-2026-53124",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "6.18.57",
            "evidence": "/affected/1/ranges"
          },
          {
            "value": "7.0.10",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "unknown",
    "structured": {
      "id": "CVE-2026-53124",
      "aliases": [
        "CVE-2026-53124"
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "728cbac5fe219d3b8a21a0688a08f2b7f8aeda2b"
                },
                {
                  "fixed": "de05e37d02f3f33ebca4967164e54f5fea809d86"
                },
                {
                  "fixed": "63335e5a67d89bb7cb9b023bbb3785896587a648"
                },
                {
                  "fixed": "0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b"
                }
              ]
            },
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "6.14.6"
                },
                {
                  "fixed": "6.15"
                }
              ]
            },
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "42ea64e01c96e594fb4f80c54dfe4f934d008a6e"
                }
              ]
            }
          ],
          "versions": [
            "v6.14.11",
            "v6.14.10",
            "v6.14.9",
            "v6.14.8",
            "v6.14.7",
            "v6.14.6"
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53124.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.15.0"
                },
                {
                  "fixed": "6.18.57"
                }
              ]
            },
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "6.19.0"
                },
                {
                  "fixed": "7.0.10"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-53124.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:26.678932042Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b",
        "https://git.kernel.org/stable/c/63335e5a67d89bb7cb9b023bbb3785896587a648",
        "https://git.kernel.org/stable/c/de05e37d02f3f33ebca4967164e54f5fea809d86",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53124.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2026-53124",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/53xxx/CVE-2026-53124.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2026-53124",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": null
  },
  "source_id": "core-osv",
  "document_id": 493198,
  "published_at": "2026-06-24T16:30:53.268+00:00"
}