blk-cgroup: fix race between policy activation and blkg destruction
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ f1c006f1c6850c14040f8337753a63119bba39b9 · < 2cf9f50a38c1839e549a08e22aa35e8d69e2c8fd| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
blk-cgroup: fix race between policy activation and blkg destruction
When switching an IO scheduler on a block device, blkcg_activate_policy() allocates blkg_policy_data (pd) for all blkgs attached to the queue. However, blkcg_activate_policy() may race with concurrent blkcg deletion, leading to use-after-free and memory leak issues.
The use-after-free occurs in the following race:
T1 (blkcg_activate_policy): - Successfully allocates pd for blkg1 (loop0->queue, blkcgA) - Fails to allocate pd for blkg2 (loop0->queue, blkcgB) - Enters the enomem rollback path to release blkg1 resources
T2 (blkcg deletion): - blkcgA is deleted concurrently - blkg1 is freed via blkg_free_workfn() - blkg1->pd is freed
T1 (continued): - Rollback path accesses blkg1->pd->online after pd is freed - Triggers use-after-free
In addition, blkg_free_workfn() frees pd before removing the blkg from q->blkg_list. This allows blkcg_activate_policy() to allocate a new pd for a blkg that is being destroyed, leaving the newly allocated pd unreachable when the blkg is finally freed.
From the CVE record · Linux
The Linux kernel’s blk-cgroup code has a race between I/O scheduler policy activation and block cgroup deletion. If these operations occur concurrently, the race can cause a use-after-free or memory leak. The input does not specify an attacker access level or required user interaction.
Engineers running the Linux kernel should check their deployments; affected versions are not specified.