CVE-2023-54268
Last modified
CVE-2023-54268 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 0.17% chance of exploitation in the next 30 days.
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.
Metrics
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872, < be646802b3dc408c4dc72a3ac32c3f4a0282414d; >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872, < fd673079749bac97bb30f1461df079e6c8e86511; >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872, < aee97eec77029270866c704f66cdf2881cbd2fe1; >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872, < d7fff52c99d52f180d8bef95d8ed8fec6343889c; >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872, < 4c088d30a72d9b8f9c6ae9362222942e4075cb00; >= 3ac7fe5a4aab409bd5674d0b070bce97f9d20872, < eb799279fb1f9c63c520fe8c1c41cb9154252db6 |
| Linux | Linux | 2.6.26 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2023-54268?
How severe is CVE-2023-54268?
How do I fix CVE-2023-54268?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2023
- CVE-2023-54262In the Linux kernel, the following vulnerability has been re…8.8
- CVE-2023-54263In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54264In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54265In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54266In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54267In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54269In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2023-5427Use After Free vulnerability in Arm Ltd Bifrost GPU Kernel D…7.8
- CVE-2023-54270In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54271In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54272In the Linux kernel, the following vulnerability has been re…
- CVE-2023-54273In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2023-54268?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
