https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 16:32:13 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-08079 bdu:2025-08079 https://cve.radiocsirt.org/vuln/bdu:2025-08079 https://cve.radiocsirt.org/vuln/bell-cve-2024-35993 <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> <p><strong>Affected:</strong> Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts</p> https://cve.radiocsirt.org/vuln/bell-cve-2024-35993 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0667 certfr-2024-avi-0667 https://cve.radiocsirt.org/vuln/certfr-2024-avi-0667 https://cve.radiocsirt.org/vuln/euvd-2026-345735 EUVD-2026-345735 https://cve.radiocsirt.org/vuln/euvd-2026-345735 https://cve.radiocsirt.org/vuln/fkie_cve-2024-35993 <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>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://cve.radiocsirt.org/vuln/fkie_cve-2024-35993 https://cve.radiocsirt.org/vuln/ghsa-q9r2-5479-5hm7 <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] Link: https://lkml.kernel.org/r/ZgGZUvsdhaT1Va-T@casper.infradead.org</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] Link: https://lkml.kernel.org/r/ZgGZUvsdhaT1Va-T@casper.infradead.org</p> https://cve.radiocsirt.org/vuln/ghsa-q9r2-5479-5hm7 https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-35993 <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 78 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm: turn folio_test_hugetlb into a PageType 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. 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. 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. [willy@infradead.org: update vmcoreinfo]</p> <p><strong>Affected:</strong> Ubuntu:16.04:LTS: linux-hwe-edge, Ubuntu:18.04:LTS: linux-aws-5.0, Ubuntu:18.04:LTS: linux-aws-5.3, Ubuntu:18.04:LTS: linux-azure, Ubuntu:18.04:LTS: linux-azure-5.3, Ubuntu:18.04:LTS: linux-azure-edge, Ubuntu:18.04:LTS: linux-gcp, Ubuntu:18.04:LTS: linux-gcp-5.3, Ubuntu:18.04:LTS: linux-gke-4.15, Ubuntu:18.04:LTS: linux-gke-5.4 and 78 more</p> <p>In the Linux kernel, the following vulnerability has been resolved: mm: turn folio_test_hugetlb into a PageType 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. 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. 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. [willy@infradead.org: update vmcoreinfo]</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-35993 https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1188 <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> <p>Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen.</p> https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1188