CVE-2026-23161 Details
Description
In the Linux kernel, the following vulnerability has been resolved: mm/shmem, swap: fix race of truncate and swap entry split The helper for shmem swap freeing is not handling the order of swap entries correctly. It uses xa_cmpxchg_irq to erase the swap entry, but it gets the entry order before that using xa_get_order without lock protection, and it may get an outdated order value if the entry is split or changed in other ways after the xa_get_order and before the xa_cmpxchg_irq. And besides, the order could grow and be larger than expected, and cause truncation to erase data beyond the end border. For example, if the target entry and following entries are swapped in or freed, then a large folio was added in place and swapped out, using the same entry, the xa_cmpxchg_irq will still succeed, it's very unlikely to happen though. To fix that, open code the Xarray cmpxchg and put the order retrieval and value checking in the same critical section. Also, ensure the order won't exceed the end border, skip it if the entry goes across the border. Skipping large swap entries crosses the end border is safe here. Shmem truncate iterates the range twice, in the first iteration, find_lock_entries already filtered such entries, and shmem will swapin the entries that cross the end border and partially truncate the folio (split the folio or at least zero part of it). So in the second loop here, if we see a swap entry that crosses the end order, it must at least have its content erased already. I observed random swapoff hangs and kernel panics when stress testing ZSWAP with shmem. After applying this patch, all problems are gone.
A race condition vulnerability has been identified in the Linux kernel's handling of swap entries for shared memory (shmem). This issue arises because the mechanism for freeing shmem swap entries does not properly manage the order of these entries. The vulnerability exists in the Linux kernel stable tree, specifically in the memory management (mm) subsystem, within the shmem component. The problem occurs when the system retrieves the order of a swap entry without adequate lock protection, potentially leading to the deletion of data beyond the intended boundary. This can happen if a large folio is added, swapped out, and then the same entry is reused, allowing the swap entry to be incorrectly processed.
Users can apply the patch available in the Linux kernel Git repository to address this vulnerability. Instructions for downloading the patched version can be found in the repository.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/8a1968bd997f45a9b11aefeabdd1232e1b6c7184 | kernel.org | Patch |
| https://git.kernel.org/stable/c/a99f9a4669a04662c8f9efe0e62cafc598153139 | kernel.org | Patch |
| https://git.kernel.org/stable/c/b23bee8cdb7aabce5701a7f57414db5a354ae8ed | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-362 | Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.12, < 6.12.69 >= 6.13, < 6.18.9 6.19 rc1 6.19 rc2 6.19 rc3 6.19 rc4 6.19 rc5 6.19 rc6 6.19 rc7 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Apr 3, 2026 | CVE Modified | kernel.org |
| Mar 18, 2026 | Initial Analysis | [email protected] |
| Feb 14, 2026 | New CVE Received | kernel.org |