Menu

Star on GitHub · 3.2k

CVE-2025-39725

5.5 · MEDIUM

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 f…

Published Sep 5, 2025CWE-476EPSS 0.15%

Overview

CVE-2025-39725 is a medium-severity vulnerability. It was published on September 5, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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_poison

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-39725?

CVE-2025-39725 is a medium-severity vulnerability. It was published on September 5, 2025 and has a CVSS 3.1 base score of 5.5 (MEDIUM).

How severe is CVE-2025-39725?

This vulnerability has a CVSS 3.1 base score of 5.5, rated MEDIUM. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-39725?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-39725?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-39725 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related MEDIUM CVEs from 2025

View all