Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2025-40006mm/hugetlb: fix folio is still mapped when deleted

Description

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 filemap_unaccount_folio. The log is as follows: BUG: Bad page cache in process hugetlb pfn:156c00 page: refcount:515 mapcount:0 mapping:0000000099fef6e1 index:0x0 pfn:0x156c00 head: order:9 mapcount:1 entire_mapcount:1 nr_pages_mapped:0 pincount:0 aops:hugetlbfs_aops ino:dcc dentry name(?):"my_hugepage_file" flags: 0x17ffffc00000c1(locked|waiters|head|node=0|zone=2|lastcpupid=0x1fffff) page_type: f4(hugetlb) page dumped because: still mapped when deleted CPU: 1 UID: 0 PID: 395 Comm: hugetlb Not tainted 6.17.0-rc5-00044-g7aac71907bde-dirty #484 NONE Hardware name: QEMU Ubuntu 24.04 PC (i440FX + PIIX, 1996), BIOS 0.0.0 02/06/2015 Call Trace: <TASK> dump_stack_lvl+0x4f/0x70 filemap_unaccount_folio+0xc4/0x1c0 __filemap_remove_folio+0x38/0x1c0 filemap_remove_folio+0x41/0xd0 remove_inode_hugepages+0x142/0x250 hugetlbfs_fallocate+0x471/0x5a0 vfs_fallocate+0x149/0x380 Hold folio lock before checking if the folio is mapped to avold race with migration.

Timeline

  1. ID reserved

    By Linux

  2. · 6 months later

    Published

  3. · 10 months later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2025-40006, by who scored it
Scored byCVSSScoreVector
LinuxCNA (assigner)3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVDNVD · Deferred3.1High7.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS (exploitation in 30 days)
0.21% · top 89% of all CVEs (19 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.

Affected products

  • Linux · Linux

    • affected 4aae8d1c051ea00b456da6811bc36d1f69de5445 – < bc1c9ce8aeff45318332035dbef9713fb9e982d7
    • affected 4aae8d1c051ea00b456da6811bc36d1f69de5445 – < 91f548e920fbf8be3f285bfa3fa045ae017e836d
    • affected 4aae8d1c051ea00b456da6811bc36d1f69de5445 – < 3e851448078f5b01f6264915df3cfef75e323a12
    • affected 4aae8d1c051ea00b456da6811bc36d1f69de5445 – < c1dc0524ab2cc3982d4e0d2bfac71a0cd4d65c39
    • affected 4aae8d1c051ea00b456da6811bc36d1f69de5445 – < c9c2a51f91aea70e89b496cac360cd795a2b3c26
    • affected 4aae8d1c051ea00b456da6811bc36d1f69de5445 – < 910d7749346c4b0acdc6e4adfdc4a9984281a206
    • affected 4aae8d1c051ea00b456da6811bc36d1f69de5445 – < 21ee79ce938127f88fe07e409c1817f477dbe7ea
    • affected 4aae8d1c051ea00b456da6811bc36d1f69de5445 – < 7b7387650dcf2881fd8bb55bcf3c8bd6c9542dd7
  • Linux · Linux

    • affected 4.5
    • unaffected < 4.5
    • unaffected 5.4.300 – ≤ 5.4.*
    • unaffected 5.10.245 – ≤ 5.10.*
    • unaffected 5.15.194 – ≤ 5.15.*
    • unaffected 6.1.155 – ≤ 6.1.*
    • unaffected 6.6.109 – ≤ 6.6.*
    • unaffected 6.12.50 – ≤ 6.12.*
    • unaffected 6.16.10 – ≤ 6.16.*
    • unaffected 6.17 – ≤ *

References

References8

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2025-40006 badge
[![CVE-2025-40006](https://cveledger.app/badge/CVE-2025-40006.svg)](https://cveledger.app/cve/CVE-2025-40006)

Record last updated .