CVE-2026-23211: mm, swap: restore swap_space attr aviod kernel panic
In the Linux kernel, the following vulnerability has been resolved:
mm, swap: restore swap_space attr aviod kernel panic
commit 8b47299a411a ("mm, swap: mark swap address space ro and add context
debug check") made the swap address space read-only. It may lead to
kernel panic if arch_prepare_to_swap returns a failure under heavy memory
pressure as follows,
el1_abort+0x40/0x64
el1h_64_sync_handler+0x48/0xcc
el1h_64_sync+0x84/0x88
errseq_set+0x4c/0xb8 (P)
__filemap_set_wb_err+0x20/0xd0
shrink_folio_list+0xc20/0x11cc
evict_folios+0x1520/0x1be4
try_to_shrink_lruvec+0x27c/0x3dc
shrink_one+0x9c/0x228
shrink_node+0xb3c/0xeac
do_try_to_free_pages+0x170/0x4f0
try_to_free_pages+0x334/0x534
__alloc_pages_direct_reclaim+0x90/0x158
__alloc_pages_slowpath+0x334/0x588
__alloc_frozen_pages_noprof+0x224/0x2fc
__folio_alloc_noprof+0x14/0x64
vma_alloc_zeroed_movable_folio+0x34/0x44
do_pte_missing+0xad4/0x1040
handle_mm_fault+0x4a4/0x790
do_page_fault+0x288/0x5f8
do_translation_fault+0x38/0x54
do_mem_abort+0x54/0xa8
Restore swap address space as not ro to avoid the panic.
Security readout for executives and security teams
Plain-English summary
This Linux kernel issue can crash an affected system when swap handling fails under heavy memory pressure. The business risk is service availability: systems may panic instead of recovering cleanly. The source bundle does not provide CVSS, confirmed exploitation, or a detailed attacker model.
Executive priority
Treat as a targeted availability risk, not an emergency exploitation event based on current evidence. Patch during the next kernel maintenance window, sooner for critical systems that frequently hit memory pressure.
Technical view
A prior Linux kernel change made swap address space read-only. If arch_prepare_to_swap fails during reclaim under heavy memory pressure, kernel paths can attempt to record writeback errors and hit a panic. The fix restores swap address space as not read-only to avoid the panic.
Likely exposure
Exposure is likely limited to Linux systems running affected kernel versions or commits identified in the CVE data, especially workloads prone to heavy memory pressure and swap activity.
Exploitation context
No active exploitation is indicated: the CVE is not in KEV, and the provided sources do not describe public exploitation. The trigger appears condition-dependent and tied to memory pressure, not a published remote attack path.
Researcher notes
The source evidence is narrow: Linux kernel CVE text and two stable commit references. There is no CVSS, CWE, exploit evidence, or detailed affected-version matrix beyond the supplied version data. Validate against downstream distribution advisories before closing exposure.
Mitigation direction
Apply Linux vendor or distribution kernel updates that include the referenced stable fixes.
Prioritize internet-facing, production, and memory-constrained Linux hosts using swap.
Review vendor advisories for exact fixed package versions in your distribution.
Use normal change control for kernel rollout and reboot requirements.
Validation and detection
Inventory Linux kernel versions across servers, containers hosts, and appliances.
Check whether deployed kernels include the referenced stable commits.
Review crash reports for kernel panics during reclaim or swap activity.
Confirm updated hosts are running the fixed kernel after reboot.
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-2026-23211 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.
0CVSS vectors
3Timeline events
0ADP providers
3Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Feb 18, 2026, 14:16 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.