CVE-2026-53124

MEDIUMNVD 5.55.5
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-24. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
1%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (2)

Auto-updated Jul 24, 2026
No patch confirmed yet.
generic

ublk: reset per-IO canceled flag on each fetch - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/63335e5a67d89bb7cb9b023bbb3785896587a648
generic

ublk: reset per-IO canceled flag on each fetch - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/0842186d2c4e67d2f8c8c2d1d779e8acffd41b5b

Vendor Advisories for CVE-2026-53124(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(8)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

All Vendor Advisories

(8)

Data Freshness Timeline

(refreshed 4× in last 7d / 58× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 172 total refreshes for this CVE.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-10 09:35 UTCEPSS rescore
  3. 2026-09-08 22:01 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-04 05:06 UTCEPSS rescore
  6. 2026-09-01 13:54 UTCEPSS rescore
  7. 2026-09-01 04:40 UTCEPSS rescore
  8. 2026-08-30 19:52 UTCEG score recompute
  9. 2026-08-30 19:52 UTCVendor advisory
  10. 2026-08-30 19:52 UTCGHSA enrichment
  11. 2026-08-30 01:22 UTCEPSS rescore
  12. 2026-08-28 21:41 UTCEPSS rescore
  13. 2026-08-28 03:41 UTCEG score recompute
  14. 2026-08-28 03:41 UTCVendor advisory
  15. 2026-08-28 03:40 UTCGHSA enrichment
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 13:20 UTCEG score recompute
  20. 2026-08-24 13:20 UTCVendor advisory
  21. 2026-08-24 13:20 UTCGHSA enrichment
  22. 2026-08-23 09:56 UTCVendor advisory
  23. 2026-08-23 09:56 UTCGHSA enrichment
  24. 2026-08-22 11:29 UTCEG score recompute
  25. 2026-08-22 11:29 UTCVendor advisory
Show 75 more
  1. 2026-08-22 11:29 UTCGHSA enrichment
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 05:42 UTCEG score recompute
  4. 2026-08-21 05:42 UTCVendor advisory
  5. 2026-08-21 05:42 UTCGHSA enrichment
  6. 2026-08-20 22:55 UTCEPSS rescore
  7. 2026-08-20 07:15 UTCEG score recompute
  8. 2026-08-20 07:15 UTCVendor advisory
  9. 2026-08-20 07:15 UTCGHSA enrichment
  10. 2026-08-19 17:04 UTCEPSS rescore
  11. 2026-08-19 01:56 UTCEG score recompute
  12. 2026-08-19 01:56 UTCVendor advisory
  13. 2026-08-19 01:56 UTCGHSA enrichment
  14. 2026-08-18 13:48 UTCEPSS rescore
  15. 2026-08-17 13:47 UTCEPSS rescore
  16. 2026-08-16 22:41 UTCEG score recompute
  17. 2026-08-16 22:41 UTCVendor advisory
  18. 2026-08-16 22:41 UTCGHSA enrichment
  19. 2026-08-16 14:56 UTCEPSS rescore
  20. 2026-08-16 02:14 UTCEPSS rescore
  21. 2026-08-16 00:15 UTCVendor advisory
  22. 2026-08-16 00:15 UTCGHSA enrichment
  23. 2026-08-15 01:48 UTCEG score recompute
  24. 2026-08-15 01:48 UTCVendor advisory
  25. 2026-08-15 01:48 UTCGHSA enrichment
  26. 2026-08-15 01:30 UTCEPSS rescore
  27. 2026-08-14 03:22 UTCEG score recompute
  28. 2026-08-14 03:22 UTCVendor advisory
  29. 2026-08-14 03:22 UTCGHSA enrichment
  30. 2026-08-13 22:00 UTCEPSS rescore
  31. 2026-08-13 04:56 UTCEG score recompute
  32. 2026-08-13 04:56 UTCVendor advisory
  33. 2026-08-13 04:56 UTCGHSA enrichment
  34. 2026-08-12 13:51 UTCEPSS rescore
  35. 2026-08-12 06:30 UTCEG score recompute
  36. 2026-08-12 06:30 UTCVendor advisory
  37. 2026-08-12 06:30 UTCGHSA enrichment
  38. 2026-08-11 08:04 UTCEG score recompute
  39. 2026-08-11 08:04 UTCVendor advisory
  40. 2026-08-11 08:04 UTCGHSA enrichment
  41. 2026-08-11 00:00 UTCEPSS rescore
  42. 2026-08-10 09:38 UTCEG score recompute
  43. 2026-08-10 09:38 UTCVendor advisory
  44. 2026-08-10 09:38 UTCGHSA enrichment
  45. 2026-08-09 13:46 UTCEPSS rescore
  46. 2026-08-09 11:12 UTCEG score recompute
  47. 2026-08-09 11:12 UTCVendor advisory
  48. 2026-08-09 11:12 UTCGHSA enrichment
  49. 2026-08-08 16:37 UTCEPSS rescore
  50. 2026-08-08 12:46 UTCEG score recompute
  51. 2026-08-08 12:46 UTCVendor advisory
  52. 2026-08-08 12:46 UTCGHSA enrichment
  53. 2026-08-07 14:19 UTCVendor advisory
  54. 2026-08-07 14:19 UTCGHSA enrichment
  55. 2026-08-06 15:53 UTCEG score recompute
  56. 2026-08-06 15:53 UTCVendor advisory
  57. 2026-08-06 15:53 UTCGHSA enrichment
  58. 2026-08-06 13:47 UTCEPSS rescore
  59. 2026-08-05 19:17 UTCEPSS rescore
  60. 2026-08-05 17:16 UTCVendor advisory
  61. 2026-08-05 17:16 UTCGHSA enrichment
  62. 2026-08-04 17:32 UTCEG score recompute
  63. 2026-08-04 17:32 UTCVendor advisory
  64. 2026-08-04 17:32 UTCGHSA enrichment
  65. 2026-08-04 15:10 UTCEPSS rescore
  66. 2026-08-04 10:39 UTCEPSS rescore
  67. 2026-08-03 19:06 UTCEG score recompute
  68. 2026-08-03 19:06 UTCVendor advisory
  69. 2026-08-03 19:06 UTCGHSA enrichment
  70. 2026-08-03 10:36 UTCEPSS rescore
  71. 2026-08-02 20:39 UTCVendor advisory
  72. 2026-08-02 20:39 UTCGHSA enrichment
  73. 2026-08-01 22:13 UTCEG score recompute
  74. 2026-08-01 22:13 UTCVendor advisory
  75. 2026-08-01 22:13 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-53124?
CVE-2026-53124 is a medium vulnerability published on June 24, 2026. 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…
When was CVE-2026-53124 disclosed?
CVE-2026-53124 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-53124 actively exploited?
CVE-2026-53124 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 99.0% of all scored CVEs.
What is the CVSS score of CVE-2026-53124?
CVE-2026-53124 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53124?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53124, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-53124

Explore →

Is Your Infrastructure Affected by CVE-2026-53124?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.