CVE-2023-54268
Description
In the Linux kernel, the following vulnerability has been resolved:
debugobjects: Don't wake up kswapd from fill_pool()
syzbot is reporting a lockdep warning in fill_pool() because the allocation from debugobjects is using GFP_ATOMIC, which is (__GFP_HIGH | __GFP_KSWAPD_RECLAIM) and therefore tries to wake up kswapd, which acquires kswapd_wait::lock.
Since fill_pool() might be called with arbitrary locks held, fill_pool() should not assume that acquiring kswapd_wait::lock is safe.
Use __GFP_HIGH instead and remove __GFP_NORETRY as it is pointless for !__GFP_DIRECT_RECLAIM allocation.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Linux kernel debugobjects fill_pool() uses GFP_ATOMIC with __GFP_KSWAPD_RECLAIM, causing lockdep warning when waking kswapd under arbitrary locks.
Root
Cause
The vulnerability resides in the debugobjects subsystem's fill_pool() function, which allocates memory using GFP_ATOMIC. This flag includes __GFP_KSWAPD_RECLAIM, causing the allocation to attempt to wake up kswapd, which acquires the kswapd_wait::lock. Since fill_pool() can be invoked while holding arbitrary locks, this can lead to a lockdep warning and potential deadlock.
Exploitation
Exploitation requires no special privileges; an attacker could trigger the code path that calls fill_pool() while holding a lock that conflicts with kswapd_wait::lock. This is likely reachable from user space via certain operations that cause debug object tracking. The syzbot fuzzer discovered this issue, indicating it can be triggered remotely or locally.
Impact
The impact is a system lockup or denial of service due to a deadlock or lockdep splat. While not directly exploitable for code execution, it can cause system instability.
Mitigation
The fix replaces GFP_ATOMIC with __GFP_HIGH and removes the unnecessary __GFP_NORETRY flag. The patch has been applied to stable kernel branches as seen in commits [1][2][3]. Users should update to the latest stable kernel.
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
6be646802b3dcfd673079749baee97eec7702d7fff52c99d54c088d30a72deb799279fb1fVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
6- git.kernel.org/stable/c/4c088d30a72d9b8f9c6ae9362222942e4075cb00nvd
- git.kernel.org/stable/c/aee97eec77029270866c704f66cdf2881cbd2fe1nvd
- git.kernel.org/stable/c/be646802b3dc408c4dc72a3ac32c3f4a0282414dnvd
- git.kernel.org/stable/c/d7fff52c99d52f180d8bef95d8ed8fec6343889cnvd
- git.kernel.org/stable/c/eb799279fb1f9c63c520fe8c1c41cb9154252db6nvd
- git.kernel.org/stable/c/fd673079749bac97bb30f1461df079e6c8e86511nvd
News mentions
0No linked articles in our index yet.