CVE-2023-52932: mm/swapfile: add cond_resched() in get_swap_pages()
In the Linux kernel, the following vulnerability has been resolved:
mm/swapfile: add cond_resched() in get_swap_pages()
The softlockup still occurs in get_swap_pages() under memory pressure. 64
CPU cores, 64GB memory, and 28 zram devices, the disksize of each zram
device is 50MB with same priority as si. Use the stress-ng tool to
increase memory pressure, causing the system to oom frequently.
The plist_for_each_entry_safe() loops in get_swap_pages() could reach tens
of thousands of times to find available space (extreme case:
cond_resched() is not called in scan_swap_map_slots()). Let's add
cond_resched() into get_swap_pages() when failed to find available space
to avoid softlockup.
Security readout for executives and security teams
Plain-English summary
CVE-2023-52932 is a Linux kernel availability bug in swap allocation. A local user can trigger heavy memory pressure that may cause a CPU soft lockup, making affected systems unresponsive. It is not described as exposing or modifying data. The supplied CVSS score is 5.5, and KEV status is false.
Executive priority
Treat as a moderate operational resilience issue. It can affect service availability on vulnerable Linux hosts, but the provided evidence requires local access and does not show data theft, data tampering, or active exploitation.
Technical view
The flaw is in get_swap_pages() in mm/swapfile. Under memory pressure, loops searching swap space may run tens of thousands of times without rescheduling, causing soft lockups. The kernel fix adds cond_resched() when available space is not found.
Likely exposure
Exposure is most relevant to Linux systems using affected kernel versions, especially hosts with swap or zram under heavy memory pressure. The CVSS vector requires local access with low privileges and has high availability impact only.
Exploitation context
The source bundle does not show active exploitation, and KEV is false. The described trigger is local memory pressure causing frequent OOM conditions and swap scanning. No remote attack path is identified in the provided sources.
Researcher notes
CWE-667 is listed. The vulnerable behavior is scheduler starvation during swap page allocation, not a memory corruption issue. Affected-version data in the bundle includes both kernel version lines and commit hashes, so verify against distro backports rather than version strings alone.
Mitigation direction
Update affected Linux kernels to versions containing the referenced stable fixes.
Follow distribution or kernel vendor guidance for exact package versions.
Prioritize shared servers where local users or workloads can exhaust memory.
Monitor for soft lockup and repeated OOM events until patched.
Validation and detection
Inventory Linux kernel versions across servers and images.
Check whether vendor kernels include one of the referenced stable fixes.
Review affected hosts for swap, zram, and memory-pressure-heavy workloads.
Confirm no reliance on KEV for prioritization; KEV is false in the bundle.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-667: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-667 · source CWE mapping
Improper Locking
Improper Locking represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.