CVE-2026-23177: mm, shmem: prevent infinite loop on truncate race
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.19% (FIRST EPSS).
- Fixed version: Linux Linux 2030dddf95451b4e7a389f052091e7c4b7b274c6, 7b6a0f121d50234aab3e7ab9a62ebe826d40a32a, dfc3ab6bd64860f8022d69903be299d09be86e11.
Low priority for now. Upgrade to Linux Linux 2030dddf95451b4e7a389f052091e7c4b7b274c6, 7b6a0f121d50234aab3e7ab9a62ebe826d40a32a, dfc3ab6bd64860f8022d69903be299d09be86e11 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 14, 2026
- Updated
- Jun 17, 2026
- EPSS
- 0.1% · 9th percentile
- CWE
- —
Report tools
Action score
0
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.12affected
- 809bc86517cc408b5b8cb8e08e69096639432bc8 and later · before dfc3ab6bd64860f8022d69903be299d09be86e11affected · git
- 809bc86517cc408b5b8cb8e08e69096639432bc8 and later · before 7b6a0f121d50234aab3e7ab9a62ebe826d40a32aaffected · git
- 809bc86517cc408b5b8cb8e08e69096639432bc8 and later · before 2030dddf95451b4e7a389f052091e7c4b7b274c6affected · git
- before 6.12not affected · semver
- 6.12.70 and later · up to and including 6.12.*not affected · semver
- 6.18.10 and later · up to and including 6.18.*not affected · semver
- 6.19 and laternot affected · original_commit_for_fix
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:13 | linux | before 6.12.73-1 | 6.12.73-1 |
| Debian:14 | linux | before 6.18.10-1 | 6.18.10-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-23174Feb 14, 2026 · nvme-pci: handle changing device dma map requirements0Monitor
- ← EarlierCVE-2026-23175Feb 14, 2026 · net: cpsw: Execute ndo_set_rx_mode callback in a work queue28Monitor
- Later →CVE-2026-23179Feb 14, 2026 · nvmet-tcp: fixup hang in nvmet_tcp_listen_data_ready()0Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 2030dddf95451b4e7a389f052091e7c4b7b274c6 | Vendor (CNA) |
| Linux Linux | 7b6a0f121d50234aab3e7ab9a62ebe826d40a32a | Vendor (CNA) |
| Linux Linux | dfc3ab6bd64860f8022d69903be299d09be86e11 | Vendor (CNA) |
| debian:linux | 6.12.73-1 · Debian:13 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.