<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 03 Oct 2026 05:53:17 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-39910 — mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-39910</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc()&lt;/p&gt;
&lt;p&gt;kasan_populate_vmalloc() and its helpers ignore the caller&amp;#39;s gfp_mask and
always allocate memory using the hardcoded GFP_KERNEL flag.  This makes
them inconsistent with vmalloc(), which was recently extended to support
GFP_NOFS and GFP_NOIO allocations.&lt;/p&gt;
&lt;p&gt;Page table allocations performed during shadow population also ignore the
external gfp_mask.  To preserve the intended semantics of GFP_NOFS and
GFP_NOIO, wrap the apply_to_page_range() calls into the appropriate
memalloc scope.&lt;/p&gt;
&lt;p&gt;xfs calls vmalloc with GFP_NOFS, so this bug could lead to deadlock.&lt;/p&gt;
&lt;p&gt;There was a report here
https://lkml.kernel.org/r/686ea951.050a0220.385921.0016.GAE@google.com&lt;/p&gt;
&lt;p&gt;This patch:
 - Extends kasan_populate_vmalloc() and helpers to take gfp_mask;
 - Passes gfp_mask down to alloc_pages_bulk() and __get_free_page();
 - Enforces GFP_NOFS/NOIO semantics with memalloc_*_save()/restore()
   around apply_to_page_range();
 - Updates vmalloc.c and percpu allocator call sites accordingly.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/vmalloc, mm/kasan: respect gfp mask in kasan_populate_vmalloc()&lt;/p&gt;
&lt;p&gt;kasan_populate_vmalloc() and its helpers ignore the caller&amp;#39;s gfp_mask and
always allocate memory using the hardcoded GFP_KERNEL flag.  This makes
them inconsistent with vmalloc(), which was recently extended to support
GFP_NOFS and GFP_NOIO allocations.&lt;/p&gt;
&lt;p&gt;Page table allocations performed during shadow population also ignore the
external gfp_mask.  To preserve the intended semantics of GFP_NOFS and
GFP_NOIO, wrap the apply_to_page_range() calls into the appropriate
memalloc scope.&lt;/p&gt;
&lt;p&gt;xfs calls vmalloc with GFP_NOFS, so this bug could lead to deadlock.&lt;/p&gt;
&lt;p&gt;There was a report here
https://lkml.kernel.org/r/686ea951.050a0220.385921.0016.GAE@google.com&lt;/p&gt;
&lt;p&gt;This patch:
 - Extends kasan_populate_vmalloc() and helpers to take gfp_mask;
 - Passes gfp_mask down to alloc_pages_bulk() and __get_free_page();
 - Enforces GFP_NOFS/NOIO semantics with memalloc_*_save()/restore()
   around apply_to_page_range();
 - Updates vmalloc.c and percpu allocator call sites accordingly.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-39910</guid>
    </item>
  </channel>
</rss>
