VDB

CVE-2025-39725

CVE-2025-39725 PUBLISHED

mm/vmscan: fix hwpoisoned large folio handling in shrink_folio_list

Reported by linux · Published September 5, 2025

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 [tujinjiang@huawei.com: add comment to unmap_poisoned_folio()]

EPSS 0.15% · 4.6th percentile

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
bpftool6.12Amazon Linux1:6.12.46-66.121.amzn2023
kernel6.12-libbpf-staticAmazon Linux1:6.12.46-66.121.amzn2023
kernel6.12-modules-extra-commonAmazon Linux1:6.12.46-66.121.amzn2023
kernel6.12-toolsAmazon Linux1:6.12.46-66.121.amzn2023
kernel6.12-libbpfAmazon Linux1:6.12.46-66.121.amzn2023
kernel6.12-headersAmazon Linux1:6.12.46-66.121.amzn2023
kernel6.12-tools-develAmazon Linux1:6.12.46-66.121.amzn2023
kernel6.12Amazon Linux1:6.12.46-66.121.amzn2023
linux_kernellinux6.15.9, 6.12.41

Risk scores

EPSS Score
0.15%
4.6th percentile

Affected products

VendorProductVersions
LinuxLinux1c9798bf8145a92abf45aa9d38a6406d9eb8bdf0, 1b0449544c6482179ac84530b61fc192a6527bfd, 1b0449544c6482179ac84530b61fc192a6527bfd
LinuxLinux6.15, 0, 6.12.41
amazon:2023bpftool6.120
amazon:2023kernel6.12-libbpf-static0
amazon:2023kernel6.12-modules-extra-common0
amazon:2023kernel6.12-tools0
amazon:2023kernel6.12-libbpf0
amazon:2023kernel6.12-headers0
amazon:2023kernel6.12-tools-devel0
amazon:2023kernel6.120
linuxlinux_kernel6.12.26, 6.14.5, 6.15
amazon:2023kernel6.12-devel0
amazon:2023perf6.120
amazon:2023python3-perf6.120
LinuxLinux6.14.5, 6.15, 1b0449544c6482179ac84530b61fc192a6527bfd
amazon:2023kernel6.12-libbpf-devel0
amazon:2023kernel-livepatch-6.12.46-66.1210
amazon:2023kernel6.12-modules-extra0

Timeline

  • Sep 5, 2025 Coalition ESS Score (17 in total, the first dated here)
  • Sep 5, 2025 CVE Published
  • Sep 6, 2025 EPSS Score (30 in total, the first dated here)
  • Dec 15, 2025 Security Advisory (138 in total, the first dated here)
  • Dec 18, 2025 PoC Published (2 in total, the first dated here)
  • Apr 20, 2026 Distribution Patch (123 in total, the first dated here)

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2025-39725
vulnetix vdb fixes CVE-2025-39725

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2025-39725/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›