CVE-2025-39725

mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list

MEDIUM
5.5
CVSS Score
Published: September 5, 2025 at 05:27 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

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()]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.12.26 ≤ v < 6.12.416.14.5 ≤ v < 6.15.91b0449544c6482179ac84530b61fc192a6527bfd1c9798bf8145a92abf45aa9d38a6406d9eb8bdf06.12.266.14.56.156.166.16 rc16.16 rc26.16 rc36.16 rc46.16 rc56.16 rc66.16 rc7912e9f0300c3564b72a8808db406e313193a37ad
Vendor states this is fixed in 656eaddbc952e1baae2f69281c22debe22140312 (fixed)
Vendor states this is fixed in 9f1e8cd0b7c4c944e9921b52a6661b5eda2705ab (fixed)
Vendor states this is fixed in c1101113d45838a823188ae25c61af97552a28ae (fixed)
Vendor states this is fixed in 6.12.41 (unaffected)
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.15.9 (unaffected)
Vendor states this is fixed in 6.16 (unaffected)

References (3)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/656eaddbc952e1baae2f69281c22debe22140312
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/9f1e8cd0b7c4c944e9921b52a6661b5eda2705ab
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/c1101113d45838a823188ae25c61af97552a28ae

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card