SECUFOCUSNOW
Home›CVE index›CVE-2025-40006
Review reviewHigh

CVE-2025-40006

Linux

In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix folio is still mapped when deleted Migration may be raced with fallocating hole. remove_inode_single_folio will unmap the folio if the folio is still mapped. However, it's called without folio lock. If the folio is migrated and the mapped pte has been converted to migration entry, folio_mapped() returns false, and won't unmap it. Due to extra refcount held by remove_inode_single_folio, migration fails, restores migration entry to normal pte, and the folio is mapped again. As a result, we triggered BUG in fil...

CVSS
7.8
EPSS
-
- percentile
CISA KEV
Not listed
Published
2025.10.21
PRIORITY ASSESSMENT

Review review

The CVSS severity warrants an early asset and exposure review.

Known exploitationNot established by KEV
Exploit probability-
Technical severityCVSS 7.8

Vulnerability overview

In the Linux kernel, the following vulnerability has been resolved: mm/hugetlb: fix folio is still mapped when deleted Migration may be raced with fallocating hole. remove_inode_single_folio will unmap the folio if the folio is still mapped. However, it's called without folio lock. If the folio is migrated and the mapped pte has been converted to migration entry, folio_mapped() returns false, and won't unmap it. Due to extra refcount held by remove_inode_single_folio, migration fails, restores migration entry to normal pte, and the folio is mapped again. As a result, we triggered BUG in fil...

Affected product and versions

Product
Linux
Affected versions
>= 4aae8d1c051ea00b456da6811bc36d1f69de5445 < bc1c9ce8aeff45318332035dbef9713fb9e982d7, >= 4aae8d1c051ea00b456da6811bc36d1f69de5445 < 91f548e920fbf8be3f285bfa3fa045ae017e836d, >= 4aae8d1c051ea00b456da6811bc36d1f69de5445 < 3e851448078f5b01f6264915df3cfef75e323a12, >= 4aae8d1c051ea00b456da6811bc36d1f69de5445 < c1dc0524ab2cc3982d4e0d2bfac71a0cd4d65c39, >= 4aae8d1c051ea00b456da6811bc36d1f69de5445 < c9c2a51f91aea70e89b496cac360cd795a2b3c26, >= 4aae8d1c051ea00b456da6811bc36d1f69de5445 < 910d7749346c4b0acdc6e4adfdc4a9984281a206, >= 4aae8d1c051ea00b456da6811bc36d1f69de5445 < 21ee79ce938127f88fe07e409c1817f477dbe7ea, >= 4aae8d1c051ea00b456da6811bc36d1f69de5445 < 7b7387650dcf2881fd8bb55bcf3c8bd6c9542dd7, >= 4.5
Fixed versions
No verified fixed-version field is available yet

Recommended response sequence

Confirm exposure before applying a vendor-supported change.

Full remediation guide
  1. 1
    Identify

    Confirm that Linux and an affected version are present.

  2. 2
    Prioritize

    Combine exploitation signals with asset exposure and business criticality.

  3. 3
    Remediate

    Follow the vendor advisory or supported update path and preserve rollback options.

  4. 4
    Verify

    Recheck the version, service health, access paths, and relevant logs.

Technical data

CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE
Not available