CVE-2022-48800: mm: vmscan: remove deadlock due to throttling failing to make progress
In the Linux kernel, the following vulnerability has been resolved:
mm: vmscan: remove deadlock due to throttling failing to make progress
A soft lockup bug in kcompactd was reported in a private bugzilla with
the following visible in dmesg;
watchdog: BUG: soft lockup - CPU#33 stuck for 26s! [kcompactd0:479]
watchdog: BUG: soft lockup - CPU#33 stuck for 52s! [kcompactd0:479]
watchdog: BUG: soft lockup - CPU#33 stuck for 78s! [kcompactd0:479]
watchdog: BUG: soft lockup - CPU#33 stuck for 104s! [kcompactd0:479]
The machine had 256G of RAM with no swap and an earlier failed
allocation indicated that node 0 where kcompactd was run was potentially
unreclaimable;
Node 0 active_anon:29355112kB inactive_anon:2913528kB active_file:0kB
inactive_file:0kB unevictable:64kB isolated(anon):0kB isolated(file):0kB
mapped:8kB dirty:0kB writeback:0kB shmem:26780kB shmem_thp:
0kB shmem_pmdmapped: 0kB anon_thp: 23480320kB writeback_tmp:0kB
kernel_stack:2272kB pagetables:24500kB all_unreclaimable? yes
Vlastimil Babka investigated a crash dump and found that a task
migrating pages was trying to drain PCP lists;
PID: 52922 TASK: ffff969f820e5000 CPU: 19 COMMAND: "kworker/u128:3"
Call Trace:
__schedule
schedule
schedule_timeout
wait_for_completion
__flush_work
__drain_all_pages
__alloc_pages_slowpath.constprop.114
__alloc_pages
alloc_migration_target
migrate_pages
migrate_to_node
do_migrate_pages
cpuset_migrate_mm_workfn
process_one_work
worker_thread
kthread
ret_from_fork
This failure is specific to CONFIG_PREEMPT=n builds. The root of the
problem is that kcompact0 is not rescheduling on a CPU while a task that
has isolated a large number of the pages from the LRU is waiting on
kcompact0 to reschedule so the pages can be released. While
shrink_inactive_list() only loops once around too_many_isolated, reclaim
can continue without rescheduling if sc->skipped_deactivate == 1 which
could happen if there was no file LRU and the inactive anon list was not
low.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can make some systems stop making progress during memory pressure, causing repeated soft lockup messages and potential service disruption. The report describes a narrow kernel scheduling and memory-reclaim failure, not data theft or remote code execution.
Executive priority
Treat as a reliability risk for affected Linux infrastructure, not a confirmed breach-enabling vulnerability. Patch through normal kernel maintenance, with higher urgency for critical systems matching the reported configuration.
Technical view
The resolved bug is in Linux mm/vmscan behavior where kcompactd can fail to reschedule while page migration waits for isolated LRU pages to be released. The source says this is specific to CONFIG_PREEMPT=n builds and observed on a large-memory system with no swap.
Likely exposure
Exposure appears limited to affected Linux 5.16-era kernels or downstream backports containing the vulnerable change, especially CONFIG_PREEMPT=n systems under severe memory pressure. Distribution-specific impact is not confirmed in the provided sources.
Exploitation context
The bundle does not show CISA KEV listing, public exploitation, exploit code, or remote attack evidence. The described trigger is an operational deadlock or soft-lockup condition during memory reclaim and page migration.
Researcher notes
Evidence is strongest for a kernel memory-management deadlock fixed upstream. The provided CVE data lacks CVSS, CWE, distribution advisories, and exploit status. Validate exposure against exact vendor kernel source or changelog, not version strings alone.
Mitigation direction
Check vendor kernel advisories for CVE-2022-48800 and applicable backports.
Upgrade to a kernel containing the referenced stable fixes or vendor equivalent.
Prioritize large-memory, no-swap, CONFIG_PREEMPT=n systems handling critical workloads.
Monitor for repeated kcompactd soft lockup messages until patched.
Validation and detection
Inventory Linux kernel versions and downstream vendor build identifiers.
Confirm whether CONFIG_PREEMPT is disabled on potentially affected hosts.
Review kernel logs for watchdog soft lockups involving kcompactd.
Verify patched kernels include the referenced stable commits or vendor backports.
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.
cve · low confidence lookup
CVE-2022-48800 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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.