All reports
Low

kernel: debugobjects: Don't wake up kswapd from fill_pool()

Affected versions

Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported
Affected versions
Unknown
Fixed version
Not reported

Exploitation

CVE-2023-54268

Probability of exploitation in the next 30 days: 0.21%

FIRST EPSS · 2026-11-18

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.

A locking issue was found in the Linux kernel's debugobjects subsystem. The fill_pool() function uses GFP_ATOMIC allocation flags, which attempt to wake up kswapd and acquire kswapd_wait::lock. Since fill_pool() may be called with arbitrary locks already held, this can trigger lockdep warnings about potential deadlocks.