| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <2025102002-CVE-2025-40006-eb23@gregkh> Date: Mon, 20 Oct 2025 17:27:02 +0200 From: Greg Kroah-Hartman <gregkh@...uxfoundation.org> To: linux-cve-announce@...r.kernel.org Cc: Greg Kroah-Hartman <gregkh@...nel.org> Subject: CVE-2025-40006: mm/hugetlb: fix folio is still mapped when deleted From: Greg Kroah-Hartman <gregkh@...nel.org> 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. The Linux kernel CVE team has assigned CVE-2025-40006 to this issue. Affected and fixed versions =========================== Issue introduced in 4.5 with commit 4aae8d1c051ea00b456da6811bc36d1f69de5445 and fixed in 5.4.300 with commit bc1c9ce8aeff45318332035dbef9713fb9e982d7 Issue introduced in 4.5 with commit 4aae8d1c051ea00b456da6811bc36d1f69de5445 and fixed in 5.10.245 with commit 91f548e920fbf8be3f285bfa3fa045ae017e836d Issue introduced in 4.5 with commit 4aae8d1c051ea00b456da6811bc36d1f69de5445 and fixed in 5.15.194 with commit 3e851448078f5b01f6264915df3cfef75e323a12 Issue introduced in 4.5 with commit 4aae8d1c051ea00b456da6811bc36d1f69de5445 and fixed in 6.1.155 with commit c1dc0524ab2cc3982d4e0d2bfac71a0cd4d65c39 Issue introduced in 4.5 with commit 4aae8d1c051ea00b456da6811bc36d1f69de5445 and fixed in 6.6.109 with commit c9c2a51f91aea70e89b496cac360cd795a2b3c26 Issue introduced in 4.5 with commit 4aae8d1c051ea00b456da6811bc36d1f69de5445 and fixed in 6.12.50 with commit 910d7749346c4b0acdc6e4adfdc4a9984281a206 Issue introduced in 4.5 with commit 4aae8d1c051ea00b456da6811bc36d1f69de5445 and fixed in 6.16.10 with commit 21ee79ce938127f88fe07e409c1817f477dbe7ea Issue introduced in 4.5 with commit 4aae8d1c051ea00b456da6811bc36d1f69de5445 and fixed in 6.17 with commit 7b7387650dcf2881fd8bb55bcf3c8bd6c9542dd7 Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-40006 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: fs/hugetlbfs/inode.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/bc1c9ce8aeff45318332035dbef9713fb9e982d7 https://git.kernel.org/stable/c/91f548e920fbf8be3f285bfa3fa045ae017e836d https://git.kernel.org/stable/c/3e851448078f5b01f6264915df3cfef75e323a12 https://git.kernel.org/stable/c/c1dc0524ab2cc3982d4e0d2bfac71a0cd4d65c39 https://git.kernel.org/stable/c/c9c2a51f91aea70e89b496cac360cd795a2b3c26 https://git.kernel.org/stable/c/910d7749346c4b0acdc6e4adfdc4a9984281a206 https://git.kernel.org/stable/c/21ee79ce938127f88fe07e409c1817f477dbe7ea https://git.kernel.org/stable/c/7b7387650dcf2881fd8bb55bcf3c8bd6c9542dd7
Powered by blists - more mailing lists