Intel

CVE-2026-53124

Linux kernel (GCP) vulnerabilities

mediumEPSS 0.1%

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

Source: UBUNTU_USNUBUNTU_USNUBUNTU_USNUBUNTU_USNUBUNTU_USNUBUNTU_USNUBUNTU_USNUBUNTU_USNUBUNTU_USNBSIBSI_CSAFCVELISTV5NVDCVEORG

Metrics

Severity
medium
Priority score
231.31
KEV status
—
Exploit maturity
no public PoC known
XIEM Effective CVSS
5.5
Source: nvd-v3
CVSS v3
5.5
CVSS v4
—
EPSS percentile
1.0 %
Low — this CVE sits in the lower 10% of all CVEs scored today.
EPSS score
0.1 %
Low — model estimates < 1% exploitation likelihood.
Published
2026-09-07 09:05 UTC
CWE
—

Reanalysis & status changes

Chronological NVD audit events for this CVE — reanalyses, CVSS updates, CPE diffs.

  1. Initial Analysis2026-07-23 20:53 UTC· nvd@nist.gov
    • CVSS V3.1: AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
    • CWE: NVD-CWE-noinfo
    • CPE Configuration: OR *cpe:2.3:o:linux:linux_kernel:6.15:rc3:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.15:rc4:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.15:rc5:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.15:rc6:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.15:rc7:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:6.15:-:*:*:*:*:*:* *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.14.6 up to (excluding) 6.15 *cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:* versions from (including) 6.15.1 up to (excluding) 7.0.10
    • Reference Type: kernel.org: https://git.kernel.org/stable/c/0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b Types: Patch
  2. New CVE Received2026-06-24 17:17 UTC· 416baaa9-dc9f-4396-8d5f-8c081fb06d67
    • Affected: Linux, Linux
    • 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).
    • Reference: https://git.kernel.org/stable/c/0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b
    • Reference: https://git.kernel.org/stable/c/63335e5a67d89bb7cb9b023bbb3785896587a648

Affected operating systems

  • linux

    redhat / enterprise_linux10.0

  • linux

    redhat / enterprise_linux7.0

  • linux

    redhat / enterprise_linux8.0

  • linux

    redhat / enterprise_linux9.0

  • linux

    ubuntu / linux-aws-6.8jammy

  • linux

    ubuntu / linux-azureresolute

  • linux

    ubuntu / linux-azuretrusty

  • linux

    ubuntu / linux-azurexenial

  • linux

    ubuntu / linux-azure-4.15bionic

  • linux

    ubuntu / linux-azure-5.4bionic

  • linux

    ubuntu / linux-azure-fdenoble

  • linux

    ubuntu / linux-azure-fderesolute

  • linux

    ubuntu / linux-azure-fde-6.8jammy

  • linux

    ubuntu / linux-azure-fipsbionic

  • linux

    ubuntu / linux-azure-fipsfocal

  • linux

    ubuntu / linux-azure-fipsnoble

  • linux

    ubuntu / linux-fipsjammy

  • linux

    ubuntu / linux-gcp-7.0noble

  • linux

    ubuntu / linux-gkejammy

  • linux

    ubuntu / linux-nvidia-tegranoble

  • linux

    ubuntu / linux-raspinoble

  • linux

    ubuntu / linux-raspi-realtimenoble

  • linux

    linux / linux_kernel2.6.12

  • linux

    linux / linux_kernel2.6.15

References & sources

Linked CVEs

Show 1392 more CVEs
IDCVE-2026-53124
Linux kernel (GCP) vulnerabilities — CVE-2026-53124 | NEOSEC Intel