CVE-2026-53126: Linux kernel · blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current()
Affects Linux kernelSource CVE Database V5
Not known to be exploited · fixed in b3e005f16cd98f815429a87aef4c61e9c140779f : update Linux kernel when convenient.
Data as of 6 Nov 2026, 16:49 UTC
Rated by Threat Radar · No CVSS score from NVD or the CNA
Thin evidence
One scorer or none- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-11-06.
- Patch
- Available – fixed in b3e005f16cd98f815429a87aef4c61e9c140779f, 23308af722fefed00af5f238024c11710938fba3, 4048ed98860d3785645ebbd34f69566a6c7320c3 +2
Exploitation evidence
Disclosed: evidence found.
CVE published 24 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in
|
| LinuxLinux | Affected
| Fixed in– |
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.
References
- git.kernel.org/stable/c/4048ed98860d3785645ebbd34f69566a6c7320c3 (opens in a new tab)
- git.kernel.org/stable/c/73a5af059905d171b398c8b2381632ee499948b5 (opens in a new tab)
- git.kernel.org/stable/c/b3e005f16cd98f815429a87aef4c61e9c140779f (opens in a new tab)
- git.kernel.org/stable/c/000e8454692cab9d1f1b80130e2870e355301d06 (opens in a new tab)
- git.kernel.org/stable/c/23308af722fefed00af5f238024c11710938fba3 (opens in a new tab)