CVE-2026-23177 Details
Description
In the Linux kernel, the following vulnerability has been resolved: mm, shmem: prevent infinite loop on truncate race When truncating a large swap entry, shmem_free_swap() returns 0 when the entry's index doesn't match the given index due to lookup alignment. The failure fallback path checks if the entry crosses the end border and aborts when it happens, so truncate won't erase an unexpected entry or range. But one scenario was ignored. When `index` points to the middle of a large swap entry, and the large swap entry doesn't go across the end border, find_get_entries() will return that large swap entry as the first item in the batch with `indices[0]` equal to `index`. The entry's base index will be smaller than `indices[0]`, so shmem_free_swap() will fail and return 0 due to the "base < index" check. The code will then call shmem_confirm_swap(), get the order, check if it crosses the END boundary (which it doesn't), and retry with the same index. The next iteration will find the same entry again at the same index with same indices, leading to an infinite loop. Fix this by retrying with a round-down index, and abort if the index is smaller than the truncate range.
A vulnerability in the Linux kernel's memory management component, specifically within the shmem (shared memory) handling, can lead to an infinite loop during the truncation of large swap entries. This issue occurs when the swap entry's index alignment causes a mismatch, prompting the shmem_free_swap() function to return 0. The fallback mechanism, designed to prevent truncation of unexpected entries, fails to account for scenarios where the index falls in the middle of a large swap entry that does not extend across the end border. As a result, the system can enter a repetitive cycle of attempting to free the same swap entry without success, effectively causing a hang in the process.
The vulnerability has been addressed in the Linux kernel. Users should upgrade to the latest version where this issue has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Feb 14, 2026References 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/2030dddf95451b4e7a389f052091e7c4b7b274c6 | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/7b6a0f121d50234aab3e7ab9a62ebe826d40a32a | kernel.org | Source CodeVendor |
| https://git.kernel.org/stable/c/dfc3ab6bd64860f8022d69903be299d09be86e11 | kernel.org | Source CodeVendor |
Weakness Enumeration
No weakness enumeration is available for this CVE.
Affected Products
| Product | Versions |
|---|---|
| Linux kernel | All versions |
CPE
Remediation
| |
Change History
2 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Feb 14, 2026 | New CVE Received | kernel.org |
Volerion