CVE-2025-39725 Details
Description
In the Linux kernel, the following vulnerability has been resolved: mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list In shrink_folio_list(), the hwpoisoned folio may be large folio, which can't be handled by unmap_poisoned_folio(). For THP, try_to_unmap_one() must be passed with TTU_SPLIT_HUGE_PMD to split huge PMD first and then retry. Without TTU_SPLIT_HUGE_PMD, we will trigger null-ptr deref of pvmw.pte. Even we passed TTU_SPLIT_HUGE_PMD, we will trigger a WARN_ON_ONCE due to the page isn't in swapcache. Since UCE is rare in real world, and race with reclaimation is more rare, just skipping the hwpoisoned large folio is enough. memory_failure() will handle it if the UCE is triggered again. This happens when memory reclaim for large folio races with memory_failure(), and will lead to kernel panic. The race is as follows: cpu0 cpu1 shrink_folio_list memory_failure TestSetPageHWPoison unmap_poisoned_folio --> trigger BUG_ON due to unmap_poisoned_folio couldn't handle large folio [[email protected]: add comment to unmap_poisoned_folio()]
A vulnerability in the Linux kernel's memory reclamation process for large folios can lead to a kernel panic. This issue arises in the 'shrink_folio_list()' function, where a hardware-poisoned large folio cannot be properly managed by the 'unmap_poisoned_folio()' function. The problem is particularly relevant for Transparent Huge Pages (THP), as 'try_to_unmap_one()' must be used with the 'TTU_SPLIT_HUGE_PMD' flag to correctly split and manage these pages. If this flag is not used, it can result in a null pointer dereference, and even with the flag, a warning is triggered because the page is not in the swap cache. The vulnerability occurs when the memory reclaim process for large folios intersects with the 'memory_failure()' function, which handles hardware errors. This race condition can cause a null pointer dereference and a subsequent kernel panic.
Users can upgrade to the patched version of the Linux kernel available in the Linux Kernel Stable Patches 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/656eaddbc952e1baae2f69281c22debe22140312 | kernel.org | Patch |
| https://git.kernel.org/stable/c/9f1e8cd0b7c4c944e9921b52a6661b5eda2705ab | kernel.org | Patch |
| https://git.kernel.org/stable/c/c1101113d45838a823188ae25c61af97552a28ae | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-476 | NULL Pointer Dereference | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.12.26, < 6.12.41 >= 6.14.5, < 6.15.9 6.16 rc1 6.16 rc2 6.16 rc3 6.16 rc4 6.16 rc5 6.16 rc6 6.16 rc7 |
CPE
Remediation
| |
Change History
3 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | kernel.org |
| Nov 25, 2025 | Initial Analysis | [email protected] |
| Sep 5, 2025 | New CVE Received | kernel.org |