CVE-2023-54088
Description
In the Linux kernel, the following vulnerability has been resolved:
blk-cgroup: hold queue_lock when removing blkg->q_node
When blkg is removed from q->blkg_list from blkg_free_workfn(), queue_lock has to be held, otherwise, all kinds of bugs(list corruption, hard lockup, ..) can be triggered from blkg_destroy_all().
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Missing queue_lock in blkg removal from blkg_free_workfn() can cause list corruption and hard lockups in Linux kernel blk-cgroup subsystem.
Vulnerability
Description
The vulnerability resides in the Linux kernel's block cgroup (blk-cgroup) implementation. When a block group (blkg) is removed from the queue's blkg list via blkg_free_workfn(), the function fails to hold the queue_lock. This missing lock can lead to concurrent modification of the linked list, resulting in list corruption or hard lockups when blkg_destroy_all() iterates over the same list.
Exploitation
Scenario
Exploitation requires local access to the system and the ability to trigger the blkg removal path. Since blkg_free_workfn() runs in a workqueue context, an attacker with sufficient privileges (or ability to cause blkg destruction) can induce a race condition. The lack of locking means that simultaneous operations on the blkg list may corrupt kernel memory, leading to a denial-of-service condition (lockup) or potentially more severe consequences.
Impact
An attacker exploiting this flaw can cause a system crash (hard lockup) or memory corruption, resulting in denial of service. Given the nature of the bug (missing lock), it is unlikely to directly lead to privilege escalation, but it can destabilize the system.
Mitigation
The fix is included in Linux kernel stable updates. Users should apply the latest stable kernel patches. The commits referenced ([1], [2]) add the missing queue_lock acquisition in blkg_free_workfn(). No workarounds are available; updating the kernel is the recommended action.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
1Patches
4b5dae1cd0d83083b58373463cd4ffdf56791c164c7bc9775Vulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
4News mentions
0No linked articles in our index yet.