CVE-2026-74482mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: mm/huge_memory: unlock i_mmap_rwsem before releasing after-split folios __folio_split() keeps dereferencing the mapping after the split: shmem_uncharge(mapping->host) and remap_page() while the folios are still frozen/locked, and i_mmap_unlock_read(mapping) at the very end, after the after-split folios have been unlocked and freed. Nothing holds an inode reference across that. The split relies on @folio -- which the beyond-EOF drop loop never removes, as it starts at folio_next(folio) -- staying locked and in the page cache to hold off eviction. But the unlock loop unlocks @folio before i_mmap_unlock_read() runs. If the caller's @lock_at is a tail beyond EOF, as memory_failure() passes when splitting a poisoned tail of a shmem THP that reaches past i_size during truncation, it too is gone from the page cache; so once @folio is unlocked no locked, in-cache folio pins the inode, and a concurrent final iput() can evict and RCU-free it before i_mmap_unlock_read() touches i_mmap_rwsem: BUG: KASAN: slab-use-after-free in __up_read+0x634/0x790 i_mmap_unlock_read include/linux/fs.h:537 [inline] __folio_split+0x732/0x1640 mm/huge_memory.c:4100 try_to_split_thp_page+0xab/0x390 mm/memory-failure.c:1675 memory_failure+0x1394/0x26e0 mm/memory-failure.c:2470 Freed by task 4601: shmem_free_in_core_inode+0x54/0xb0 mm/shmem.c:5177 evict+0x57f/0xac0 fs/inode.c:870 Do every mapping dereference while @folio still pins the inode: drop i_mmap_rwsem right after remap_page(), before the loop that unlocks and frees the after-split folios, and clear @mapping so the exit path does not unlock it again. shmem_uncharge() and remap_page() already run before that point, so after this nothing past the unlock loop touches the inode or the mapping. This is now a rule the split depends on, alongside keeping @folio frozen until the page cache is updated: no inode or mapping dereference once the after-split folios start being unlocked.
Timeline
ID reserved
By Linux
Published
- 2 months later
· 2 months later
Record updated
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Received | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (16 Nov 2026)
- CISA SSVC
- Exploitation: none · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected baa355fd331424526e742d41d9b90d5f9d10f716 – < bc2f5eabaaf60ec18da70b619a8fba1bfb7dea3a
- affected baa355fd331424526e742d41d9b90d5f9d10f716 – < f87c08060818ebb19bafed37c38244538da25097
- affected baa355fd331424526e742d41d9b90d5f9d10f716 – < 6f5c272d71845a669e4c8ee5c72b376e29a0e6e5
- affected baa355fd331424526e742d41d9b90d5f9d10f716 – < be106f7855f03d3128ed0ce70ba74b484a90b473
- affected baa355fd331424526e742d41d9b90d5f9d10f716 – < e3dd774dbfd0b5bc2dbd0995221751b1234f8205
- affected baa355fd331424526e742d41d9b90d5f9d10f716 – < 10065fb891651d9541e7a5a2db84c1e656ece4f9
- affected baa355fd331424526e742d41d9b90d5f9d10f716 – < d640efe94d86d3be893d4c19220362546a637e90
- affected baa355fd331424526e742d41d9b90d5f9d10f716 – < e923bd21058ea02fd0dcd3549d151d143fd036e5
- affected 4.8
- unaffected < 4.8
- unaffected 5.10.265 – ≤ 5.10.*
- unaffected 5.15.216 – ≤ 5.15.*
- unaffected 6.1.183 – ≤ 6.1.*
- unaffected 6.6.151 – ≤ 6.6.*
- unaffected 6.12.103 – ≤ 6.12.*
- unaffected 6.18.44 – ≤ 6.18.*
- unaffected 7.1.8 – ≤ 7.1.*
- unaffected 7.2 – ≤ *
References
References8
- https://git.kernel.org/stable/c/bc2f5eabaaf60ec18da70b619a8fba1bfb7dea3a (opens in a new tab)
- https://git.kernel.org/stable/c/f87c08060818ebb19bafed37c38244538da25097 (opens in a new tab)
- https://git.kernel.org/stable/c/6f5c272d71845a669e4c8ee5c72b376e29a0e6e5 (opens in a new tab)
- https://git.kernel.org/stable/c/be106f7855f03d3128ed0ce70ba74b484a90b473 (opens in a new tab)
- https://git.kernel.org/stable/c/e3dd774dbfd0b5bc2dbd0995221751b1234f8205 (opens in a new tab)
- https://git.kernel.org/stable/c/10065fb891651d9541e7a5a2db84c1e656ece4f9 (opens in a new tab)
- https://git.kernel.org/stable/c/d640efe94d86d3be893d4c19220362546a637e90 (opens in a new tab)
- https://git.kernel.org/stable/c/e923bd21058ea02fd0dcd3549d151d143fd036e5 (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-59675 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-74482)Record last updated .