CVE-2026-53126
blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current()
Description
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.
INFO
Published Date :
June 24, 2026, 5:17 p.m.
Last Modified :
July 14, 2026, 3:26 p.m.
Remotely Exploit :
No
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Solution
- Apply kernel patches that restore missing put_disk() calls.
- Ensure disk references are correctly released on error paths.
- Update the Linux kernel to the latest patched version.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2026-53126.
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2026-53126 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2026-53126
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2026-53126 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2026-53126 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jun. 24, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': 'f05837ed73d0c73e950b2d9f2612febb0d3d451e', 'lessThan': '4048ed98860d3785645ebbd34f69566a6c7320c3', 'versionType': 'git'}, {'status': 'affected', 'version': 'f05837ed73d0c73e950b2d9f2612febb0d3d451e', 'lessThan': '73a5af059905d171b398c8b2381632ee499948b5', 'versionType': 'git'}, {'status': 'affected', 'version': 'f05837ed73d0c73e950b2d9f2612febb0d3d451e', 'lessThan': 'b3e005f16cd98f815429a87aef4c61e9c140779f', 'versionType': 'git'}, {'status': 'affected', 'version': 'f05837ed73d0c73e950b2d9f2612febb0d3d451e', 'lessThan': '000e8454692cab9d1f1b80130e2870e355301d06', 'versionType': 'git'}, {'status': 'affected', 'version': 'f05837ed73d0c73e950b2d9f2612febb0d3d451e', 'lessThan': '23308af722fefed00af5f238024c11710938fba3', 'versionType': 'git'}], 'programFiles': ['block/blk-cgroup.c'], 'defaultStatus': 'unaffected'}, {'repo': 'https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git', 'vendor': 'Linux', 'product': 'Linux', 'versions': [{'status': 'affected', 'version': '6.3'}, {'status': 'unaffected', 'version': '0', 'lessThan': '6.3', 'versionType': 'semver'}, {'status': 'unaffected', 'version': '6.6.141', 'versionType': 'semver', 'lessThanOrEqual': '6.6.*'}, {'status': 'unaffected', 'version': '6.12.91', 'versionType': 'semver', 'lessThanOrEqual': '6.12.*'}, {'status': 'unaffected', 'version': '6.18.33', 'versionType': 'semver', 'lessThanOrEqual': '6.18.*'}, {'status': 'unaffected', 'version': '7.0.10', 'versionType': 'semver', 'lessThanOrEqual': '7.0.*'}, {'status': 'unaffected', 'version': '7.1', 'versionType': 'original_commit_for_fix', 'lessThanOrEqual': '*'}], 'programFiles': ['block/blk-cgroup.c'], 'defaultStatus': 'affected'}] Added Description 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. Added Reference https://git.kernel.org/stable/c/000e8454692cab9d1f1b80130e2870e355301d06 Added Reference https://git.kernel.org/stable/c/23308af722fefed00af5f238024c11710938fba3 Added Reference https://git.kernel.org/stable/c/4048ed98860d3785645ebbd34f69566a6c7320c3 Added Reference https://git.kernel.org/stable/c/73a5af059905d171b398c8b2381632ee499948b5 Added Reference https://git.kernel.org/stable/c/b3e005f16cd98f815429a87aef4c61e9c140779f