debugobjects: Don't wake up kswapd from fill_pool()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3ac7fe5a4aab409bd5674d0b070bce97f9d20872 · < eb799279fb1f9c63c520fe8c1c41cb9154252db6| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel's debugobjects fill_pool() can trigger a lockdep warning by waking kswapd while arbitrary locks are held. The input does not describe an attacker path or specify network access, authentication, or user interaction requirements.
Engineers running Linux kernels with debugobjects should check their versions; affected versions are not specified.