CVE-2023-54268
published 2025-12-30CVE-2023-54268: 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…
PriorityP423low2.5
EPSS
0.18%
7.7th percentile
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
17 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 6.1.37-1 (bookworm) | linux 6.1.37-1 (bookworm) |
| linux | linux | — | — |
| linux | linux | >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872 < be646802b3dc408c4dc72a3ac32c3f4a0282414d | be646802b3dc408c4dc72a3ac32c3f4a0282414d |
| linux | linux | >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872 < fd673079749bac97bb30f1461df079e6c8e86511 | fd673079749bac97bb30f1461df079e6c8e86511 |
| linux | linux | >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872 < aee97eec77029270866c704f66cdf2881cbd2fe1 | aee97eec77029270866c704f66cdf2881cbd2fe1 |
| linux | linux | >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872 < d7fff52c99d52f180d8bef95d8ed8fec6343889c | d7fff52c99d52f180d8bef95d8ed8fec6343889c |
| linux | linux | >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872 < 4c088d30a72d9b8f9c6ae9362222942e4075cb00 | 4c088d30a72d9b8f9c6ae9362222942e4075cb00 |
| linux | linux | >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872 < eb799279fb1f9c63c520fe8c1c41cb9154252db6 | eb799279fb1f9c63c520fe8c1c41cb9154252db6 |
| linux | linux_kernel | >= 0 < 5.10.191-1 | 5.10.191-1 |
| linux | linux_kernel | >= 0 < 6.1.37-1 | 6.1.37-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 0 < 6.3.7-1 | 6.3.7-1 |
| linux | linux_kernel | >= 2.6.26 < 5.4.244 | 5.4.244 |
| linux | linux_kernel | >= 5.11.0 < 5.15.114 | 5.15.114 |
| linux | linux_kernel | >= 5.16.0 < 6.1.31 | 6.1.31 |
| linux | linux_kernel | >= 5.5.0 < 5.10.181 | 5.10.181 |
| linux | linux_kernel | >= 6.2.0 < 6.3.5 | 6.3.5 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2023-54268: In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don't wake up kswapd from fill_pool() syzbot is reporting a lockdep
osv·2025-12-30
CVE-2023-54268 CVE-2023-54268: In the Linux kernel, the following vulnerability has been resolved: debugobjects: Don't wake up kswapd from fill_pool() syzbot is reporting a lockdep
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.
GHSA
GHSA-wfjg-crvw-f25h: In the Linux kernel, the following vulnerability has been resolved:
debugobjects: Don't wake up kswapd from fill_pool()
syzbot is reporting a lockde
ghsa_unreviewed·2025-12-30
CVE-2023-54268 GHSA-wfjg-crvw-f25h: In the Linux kernel, the following vulnerability has been resolved:
debugobjects: Don't wake up kswapd from fill_pool()
syzbot is reporting a lockde
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.
OSV
debugobjects: Don't wake up kswapd from fill_pool()
osv·2025-12-30
CVE-2023-54268 debugobjects: Don't wake up kswapd from fill_pool()
debugobjects: Don't wake up kswapd from fill_pool()
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.
Red Hat
kernel: debugobjects: Don't wake up kswapd from fill_pool()
vendor_redhat·2025-12-30·CVSS 2.5
CVE-2023-54268 [LOW] CWE-833 kernel: debugobjects: Don't wake up kswapd from fill_pool()
kernel: debugobjects: Don't wake up kswapd from fill_pool()
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
Debian
CVE-2023-54268: linux - In the Linux kernel, the following vulnerability has been resolved: debugobject...
vendor_debian·2023
CVE-2023-54268 CVE-2023-54268: linux - In the Linux kernel, the following vulnerability has been resolved: debugobject...
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.
Scope: local
bookworm: resolved (fixed in 6.1.37-1)
bullseye: resolved (fixed in 5.10.191-1)
forky: resolved (fixed in 6.3.7-1)
sid: resolved (fixed in 6.3.7-1)
trixie: resolved (fixed in 6.3.7-1)
No detection rules found.
No public exploits indexed.
Wiz
CVE-2023-54268 Impact, Exploitability, and Mitigation Steps | Wiz
blogs_wiz
CVE-2023-54268 CVE-2023-54268 Impact, Exploitability, and Mitigation Steps | Wiz
## CVE-2023-54268 :
Linux Kernel vulnerability analysis and mitigation
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.
Source : NVD
Published December 30, 2025
CNA Score N/A
Affected Technologies
Linux Kernel
Linux Debian
Has Public Exploit No
Bugzilla
CVE-2023-54268 kernel: debugobjects: Don't wake up kswapd from fill_pool()
bugzilla·2025-12-30
CVE-2023-54268 [LOW] CVE-2023-54268 kernel: debugobjects: Don't wake up kswapd from fill_pool()
CVE-2023-54268 kernel: debugobjects: Don't wake up kswapd from fill_pool()
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.
Discussion:
Upstream advisory:
https://lore.kernel.org/linux-cve-announce/2025123000-CVE-2023-54268-3ba2@gregkh/T
https://git.kernel.org/stable/c/4c088d30a72d9b8f9c6ae9362222942e4075cb00https://git.kernel.org/stable/c/aee97eec77029270866c704f66cdf2881cbd2fe1https://git.kernel.org/stable/c/be646802b3dc408c4dc72a3ac32c3f4a0282414dhttps://git.kernel.org/stable/c/d7fff52c99d52f180d8bef95d8ed8fec6343889chttps://git.kernel.org/stable/c/eb799279fb1f9c63c520fe8c1c41cb9154252db6https://git.kernel.org/stable/c/fd673079749bac97bb30f1461df079e6c8e86511
2025-12-30
Published