Answer in brief
CVE-2026-53126 records a Unknown severity vulnerability in blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current(). The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=f05837ed73d0c73e950b2d9f2612febb0d3d451e <4048ed98860d3785645ebbd34f69566a6c7320c3 || >=f05837ed73d0c73e950b2d9f2612febb0d3d451e <73a5af059905d171b398c8b2381632ee499948b5 || >=f05837ed73d0c73e950b2d9f2612febb0d3d451e <b3e005f16cd98f815429a87aef4c61e9c140779f || >=f05837ed73d0c73e950b2d9f2612febb0d3d451e <000e8454692cab9d1f1b80130e2870e355301d06 || >=f05837ed73d0c73e950b2d9f2612febb0d3d451e <23308af722fefed00af5f238024c11710938fba3 | 4048ed98860d3785645ebbd34f69566a6c7320c3, 73a5af059905d171b398c8b2381632ee499948b5, b3e005f16cd98f815429a87aef4c61e9c140779f, 000e8454692cab9d1f1b80130e2870e355301d06, 23308af722fefed00af5f238024c11710938fba3 |
| Linux/Linuxgeneric | 6.3 | Not reported |
Published upstream
Jun 24, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jun 24, 2026
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.
Quoted source text, attributed separately from HOL analysis.