CVE-2023-54268

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

N/A
Published: December 30, 2025 at 12:15 PM UTC
Updated: June 17, 2026 at 06:47 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

2.6.26 ≤ v < 5.10.1812.6.26 ≤ v < 5.15.1142.6.26 ≤ v < 5.4.2442.6.26 ≤ v < 6.1.312.6.26 ≤ v < 6.3.52.6.26 ≤ v < 6.42.6.263ac7fe5a4aab409bd5674d0b070bce97f9d20872
Vendor states this is fixed in 4c088d30a72d9b8f9c6ae9362222942e4075cb00 (fixed)
Vendor states this is fixed in aee97eec77029270866c704f66cdf2881cbd2fe1 (fixed)
Vendor states this is fixed in be646802b3dc408c4dc72a3ac32c3f4a0282414d (fixed)
Vendor states this is fixed in d7fff52c99d52f180d8bef95d8ed8fec6343889c (fixed)
Vendor states this is fixed in eb799279fb1f9c63c520fe8c1c41cb9154252db6 (fixed)
Vendor states this is fixed in fd673079749bac97bb30f1461df079e6c8e86511 (fixed)
Vendor states this is fixed in 2.6.26 (unaffected)
Vendor states this is fixed in 5.10.181 (unaffected)
Vendor states this is fixed in 5.15.114 (unaffected)
Vendor states this is fixed in 5.4.244 (unaffected)
Vendor states this is fixed in 6.1.31 (unaffected)
Vendor states this is fixed in 6.3.5 (unaffected)
Vendor states this is fixed in 6.4 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusDEFERRED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card