CVE-2025-39725
Last modified
CVE-2025-39725 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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. EPSS estimates a 0.14% chance of exploitation in the next 30 days.
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 [tujinjiang@huawei.com: add comment to unmap_poisoned_folio()]
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions | Update |
|---|---|---|---|
| Linux | Linux Kernel | >= 6.12.26, < 6.12.41 | — |
| Linux | Linux Kernel | >= 6.14.5, < 6.15.9 | — |
| Linux | Linux Kernel | 6.16 | Rc1 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2025-39725?
How severe is CVE-2025-39725?
How do I fix CVE-2025-39725?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2025
- CVE-2025-3972A vulnerability, which was classified as critical, has been …9.8
- CVE-2025-39720In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39721In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39722In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39723In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39724In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39726In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2025-39727In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2025-39728In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-39729In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2025-3973A vulnerability, which was classified as critical, was found…9.8
- CVE-2025-39730In the Linux kernel, the following vulnerability has been re…7.8
Are you affected by CVE-2025-39725?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
