CVE-2026-53126

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:

blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current()

Add the missing put_disk() on the error path in blkcg_maybe_throttle_current(). When blkcg lookup, blkg lookup, or blkg_tryget() fails, the function jumps to the out label which only calls rcu_read_unlock() but does not release the disk reference acquired by blkcg_schedule_throttle() via get_device(). Since current->throttle_disk is already set to NULL before the lookup, blkcg_exit() cannot release this reference either, causing the disk to never be freed.

Restore the reference release that was present as blk_put_queue() in the original code but was inadvertently dropped during the conversion from request_queue to gendisk.

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
2%
KEV
Not listed

Published

June 24, 2026

Last Modified

July 23, 2026

Advisory Details (5)

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

blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/b3e005f16cd98f815429a87aef4c61e9c140779f
generic

blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/73a5af059905d171b398c8b2381632ee499948b5
generic

blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4048ed98860d3785645ebbd34f69566a6c7320c3
generic

blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/23308af722fefed00af5f238024c11710938fba3
generic

blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current() - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/000e8454692cab9d1f1b80130e2870e355301d06

Vendor Advisories for CVE-2026-53126(2)

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

Patch Availability(22)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-28.28) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-lowlatency-64k-6.8 (6.8.0-1059.62.1) @ noble2026-08-30ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-30ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-7.0 (7.0.0-1008.8) @ resolute2026-08-30ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-30ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-30ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1015.15) @ resolute2026-08-30ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-30ubuntu
ubuntulinux-xilinx-zynqmp (6.8.0.1033.34) @ noble2026-08-30ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-nvidia-hwe-26.04 (7.0.0-2016.16) @ resolute2026-08-30ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-30ubuntu

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

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.94-1~bpo12+1 (27 versions)6.12.94-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.9-1~bpo13+1 (140 versions)7.0.10-1

Additional Vendor Advisories

(22)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-53126?
CVE-2026-53126 is a medium vulnerability published on June 24, 2026. In the Linux kernel, the following vulnerability has been resolved: blk-cgroup: fix disk reference leak in blkcgmaybethrottle_current() Add the missing put_disk() on the error path in blkcgmaybethrottle_current(). When blkcg lookup, blkg lookup, or blkg_tryget() fails, the function jumps to the out…
When was CVE-2026-53126 disclosed?
CVE-2026-53126 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-53126 actively exploited?
CVE-2026-53126 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 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-53126?
CVE-2026-53126 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-53126?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-53126, 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-53126

Explore →

Is Your Infrastructure Affected by CVE-2026-53126?

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