https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 21:22:26 +0000 https://vulnerability.circl.lu/vuln/cve-2024-35993 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: turn folio_test_hugetlb into a PageType</p> <p>The current folio_test_hugetlb() can be fooled by a concurrent folio split into returning true for a folio which has never belonged to hugetlbfs. This can&#39;t happen if the caller holds a refcount on it, but we have a few places (memory-failure, compaction, procfs) which do not and should not take a speculative reference.</p> <p>Since hugetlb pages do not use individual page mapcounts (they are always fully mapped and use the entire_mapcount field to record the number of mappings), the PageType field is available now that page_mapcount() ignores the value in this field.</p> <p>In compaction and with CONFIG_DEBUG_VM enabled, the current implementation can result in an oops, as reported by Luis. This happens since 9c5ccf2db04b (&#34;mm: remove HUGETLB_PAGE_DTOR&#34;) effectively added some VM_BUG_ON() checks in the PageHuge() testing path.</p> <p>[willy@infradead.org: update vmcoreinfo]</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>mm: turn folio_test_hugetlb into a PageType</p> <p>The current folio_test_hugetlb() can be fooled by a concurrent folio split into returning true for a folio which has never belonged to hugetlbfs. This can&#39;t happen if the caller holds a refcount on it, but we have a few places (memory-failure, compaction, procfs) which do not and should not take a speculative reference.</p> <p>Since hugetlb pages do not use individual page mapcounts (they are always fully mapped and use the entire_mapcount field to record the number of mappings), the PageType field is available now that page_mapcount() ignores the value in this field.</p> <p>In compaction and with CONFIG_DEBUG_VM enabled, the current implementation can result in an oops, as reported by Luis. This happens since 9c5ccf2db04b (&#34;mm: remove HUGETLB_PAGE_DTOR&#34;) effectively added some VM_BUG_ON() checks in the PageHuge() testing path.</p> <p>[willy@infradead.org: update vmcoreinfo]</p> https://vulnerability.circl.lu/vuln/cve-2024-35993