Bug 2492412 (CVE-2026-53126) - CVE-2026-53126 kernel: blk-cgroup: fix disk reference leak in blkcg_maybe_throttle_current()
Summary: CVE-2026-53126 kernel: blk-cgroup: fix disk reference leak in blkcg_maybe_thr...
Keywords:
Status: NEW
Alias: CVE-2026-53126
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-06-24 18:10 UTC by OSIDB Bzimport
Modified: 2026-06-24 19:13 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-06-24 18:10:52 UTC
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.

Comment 1 Mauro Matteo Cascella 2026-06-24 19:09:19 UTC
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2026062417-CVE-2026-53126-f288@gregkh/T


Note You need to log in before you can comment on or make changes to this bug.