<?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://cve.radiocsirt.org</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>Tue, 17 Nov 2026 10:10:01 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98920</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98920</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98920</guid>
    </item>
    <item>
      <title>EUVD-2026-391518</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-391518</link>
      <description>EUVD-2026-391518</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-391518</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98920</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98920</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix missing alloc tagging of direct mempool allocations&lt;/p&gt;
&lt;p&gt;Commit 1d78d56c43ef (&amp;#34;netfs: Fix folio_queue ENOMEM in writeback by
adding a mempool&amp;#34;) added a mempool for the folio_queues and made the
request, subrequest and folio_queue allocations distinguish between
writeback and everything else.  Writeback is part of memory reclaim
and must not fail due to ENOMEM, so it allocates under GFP_NOFS
through mempool_alloc(), which may dip into the pool&amp;#39;s reserve and,
if that runs empty, wait for elements to be returned.  The
GFP_KERNEL paths, which can return -ENOMEM to their callers, invoke
the pool&amp;#39;s -&amp;gt;alloc() callback directly instead.&lt;/p&gt;
&lt;p&gt;The direct call, however, skips the alloc_hooks() wrapper that the
mempool_alloc() macro provides.  The pool callbacks, mempool_alloc_slab()
and mempool_kmalloc(), call kmem_cache_alloc_noprof() and kmalloc_noprof()
and rely on current-&amp;gt;alloc_tag having been set by the caller.  With
CONFIG_MEM_ALLOC_PROFILING_DEBUG=y this leads to&lt;/p&gt;
&lt;p&gt;current-&amp;gt;alloc_tag not set
    WARNING: ./include/linux/alloc_tag.h:161 at __alloc_tagging_slab_alloc_hook
    alloc_tag was not set
    WARNING: ./include/linux/alloc_tag.h:166 at __alloc_tagging_slab_free_hook&lt;/p&gt;
&lt;p&gt;at allocation and free time respectively, as reported when reading
files on a CIFS mount.  The allocations are also missing from
/proc/allocinfo.&lt;/p&gt;
&lt;p&gt;Wrap the direct -&amp;gt;alloc() invocations in alloc_hooks() with a new
mempool_alloc_noreser…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix missing alloc tagging of direct mempool allocations&lt;/p&gt;
&lt;p&gt;Commit 1d78d56c43ef (&amp;#34;netfs: Fix folio_queue ENOMEM in writeback by
adding a mempool&amp;#34;) added a mempool for the folio_queues and made the
request, subrequest and folio_queue allocations distinguish between
writeback and everything else.  Writeback is part of memory reclaim
and must not fail due to ENOMEM, so it allocates under GFP_NOFS
through mempool_alloc(), which may dip into the pool&amp;#39;s reserve and,
if that runs empty, wait for elements to be returned.  The
GFP_KERNEL paths, which can return -ENOMEM to their callers, invoke
the pool&amp;#39;s -&amp;gt;alloc() callback directly instead.&lt;/p&gt;
&lt;p&gt;The direct call, however, skips the alloc_hooks() wrapper that the
mempool_alloc() macro provides.  The pool callbacks, mempool_alloc_slab()
and mempool_kmalloc(), call kmem_cache_alloc_noprof() and kmalloc_noprof()
and rely on current-&amp;gt;alloc_tag having been set by the caller.  With
CONFIG_MEM_ALLOC_PROFILING_DEBUG=y this leads to&lt;/p&gt;
&lt;p&gt;current-&amp;gt;alloc_tag not set
    WARNING: ./include/linux/alloc_tag.h:161 at __alloc_tagging_slab_alloc_hook
    alloc_tag was not set
    WARNING: ./include/linux/alloc_tag.h:166 at __alloc_tagging_slab_free_hook&lt;/p&gt;
&lt;p&gt;at allocation and free time respectively, as reported when reading
files on a CIFS mount.  The allocations are also missing from
/proc/allocinfo.&lt;/p&gt;
&lt;p&gt;Wrap the direct -&amp;gt;alloc() invocations in alloc_hooks() with a new
mempool_alloc_noreser…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98920</guid>
    </item>
    <item>
      <title>GHSA-c3hx-25rr-8x92</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-c3hx-25rr-8x92</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix missing alloc tagging of direct mempool allocations&lt;/p&gt;
&lt;p&gt;Commit 1d78d56c43ef (&amp;#34;netfs: Fix folio_queue ENOMEM in writeback by
adding a mempool&amp;#34;) added a mempool for the folio_queues and made the
request, subrequest and folio_queue allocations distinguish between
writeback and everything else.  Writeback is part of memory reclaim
and must not fail due to ENOMEM, so it allocates under GFP_NOFS
through mempool_alloc(), which may dip into the pool&amp;#39;s reserve and,
if that runs empty, wait for elements to be returned.  The
GFP_KERNEL paths, which can return -ENOMEM to their callers, invoke
the pool&amp;#39;s -&amp;gt;alloc() callback directly instead.&lt;/p&gt;
&lt;p&gt;The direct call, however, skips the alloc_hooks() wrapper that the
mempool_alloc() macro provides.  The pool callbacks, mempool_alloc_slab()
and mempool_kmalloc(), call kmem_cache_alloc_noprof() and kmalloc_noprof()
and rely on current-&amp;gt;alloc_tag having been set by the caller.  With
CONFIG_MEM_ALLOC_PROFILING_DEBUG=y this leads to&lt;/p&gt;
&lt;p&gt;current-&amp;gt;alloc_tag not set
    WARNING: ./include/linux/alloc_tag.h:161 at __alloc_tagging_slab_alloc_hook
    alloc_tag was not set
    WARNING: ./include/linux/alloc_tag.h:166 at __alloc_tagging_slab_free_hook&lt;/p&gt;
&lt;p&gt;at allocation and free time respectively, as reported when reading
files on a CIFS mount.  The allocations are also missing from
/proc/allocinfo.&lt;/p&gt;
&lt;p&gt;Wrap the direct -&amp;gt;alloc() invocations in alloc_hooks() with a new
mempool_alloc_noreser…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;netfs: Fix missing alloc tagging of direct mempool allocations&lt;/p&gt;
&lt;p&gt;Commit 1d78d56c43ef (&amp;#34;netfs: Fix folio_queue ENOMEM in writeback by
adding a mempool&amp;#34;) added a mempool for the folio_queues and made the
request, subrequest and folio_queue allocations distinguish between
writeback and everything else.  Writeback is part of memory reclaim
and must not fail due to ENOMEM, so it allocates under GFP_NOFS
through mempool_alloc(), which may dip into the pool&amp;#39;s reserve and,
if that runs empty, wait for elements to be returned.  The
GFP_KERNEL paths, which can return -ENOMEM to their callers, invoke
the pool&amp;#39;s -&amp;gt;alloc() callback directly instead.&lt;/p&gt;
&lt;p&gt;The direct call, however, skips the alloc_hooks() wrapper that the
mempool_alloc() macro provides.  The pool callbacks, mempool_alloc_slab()
and mempool_kmalloc(), call kmem_cache_alloc_noprof() and kmalloc_noprof()
and rely on current-&amp;gt;alloc_tag having been set by the caller.  With
CONFIG_MEM_ALLOC_PROFILING_DEBUG=y this leads to&lt;/p&gt;
&lt;p&gt;current-&amp;gt;alloc_tag not set
    WARNING: ./include/linux/alloc_tag.h:161 at __alloc_tagging_slab_alloc_hook
    alloc_tag was not set
    WARNING: ./include/linux/alloc_tag.h:166 at __alloc_tagging_slab_free_hook&lt;/p&gt;
&lt;p&gt;at allocation and free time respectively, as reported when reading
files on a CIFS mount.  The allocations are also missing from
/proc/allocinfo.&lt;/p&gt;
&lt;p&gt;Wrap the direct -&amp;gt;alloc() invocations in alloc_hooks() with a new
mempool_alloc_noreser…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-c3hx-25rr-8x92</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98920</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98920</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing alloc tagging of direct mempool allocations Commit 1d78d56c43ef (&amp;#34;netfs: Fix folio_queue ENOMEM in writeback by adding a mempool&amp;#34;) added a mempool for the folio_queues and made the request, subrequest and folio_queue allocations distinguish between writeback and everything else.  Writeback is part of memory reclaim and must not fail due to ENOMEM, so it allocates under GFP_NOFS through mempool_alloc(), which may dip into the pool&amp;#39;s reserve and, if that runs empty, wait for elements to be returned.  The GFP_KERNEL paths, which can return -ENOMEM to their callers, invoke the pool&amp;#39;s -&amp;gt;alloc() callback directly instead. The direct call, however, skips the alloc_hooks() wrapper that the mempool_alloc() macro provides.  The pool callbacks, mempool_alloc_slab() and mempool_kmalloc(), call kmem_cache_alloc_noprof() and kmalloc_noprof() and rely on current-&amp;gt;alloc_tag having been set by the caller.  With CONFIG_MEM_ALLOC_PROFILING_DEBUG=y this leads to     current-&amp;gt;alloc_tag not set     WARNING: ./include/linux/alloc_tag.h:161 at __alloc_tagging_slab_alloc_hook     alloc_tag was not set     WARNING: ./include/linux/alloc_tag.h:166 at __alloc_tagging_slab_free_hook at allocation and free time respectively, as reported when reading files on a CIFS mount.  The allocations are also missing from /proc/allocinfo. Wrap the direct -&amp;gt;alloc() invocations in alloc_hooks() with a new mempool_alloc_noreserve() h…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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 96 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: netfs: Fix missing alloc tagging of direct mempool allocations Commit 1d78d56c43ef (&amp;#34;netfs: Fix folio_queue ENOMEM in writeback by adding a mempool&amp;#34;) added a mempool for the folio_queues and made the request, subrequest and folio_queue allocations distinguish between writeback and everything else.  Writeback is part of memory reclaim and must not fail due to ENOMEM, so it allocates under GFP_NOFS through mempool_alloc(), which may dip into the pool&amp;#39;s reserve and, if that runs empty, wait for elements to be returned.  The GFP_KERNEL paths, which can return -ENOMEM to their callers, invoke the pool&amp;#39;s -&amp;gt;alloc() callback directly instead. The direct call, however, skips the alloc_hooks() wrapper that the mempool_alloc() macro provides.  The pool callbacks, mempool_alloc_slab() and mempool_kmalloc(), call kmem_cache_alloc_noprof() and kmalloc_noprof() and rely on current-&amp;gt;alloc_tag having been set by the caller.  With CONFIG_MEM_ALLOC_PROFILING_DEBUG=y this leads to     current-&amp;gt;alloc_tag not set     WARNING: ./include/linux/alloc_tag.h:161 at __alloc_tagging_slab_alloc_hook     alloc_tag was not set     WARNING: ./include/linux/alloc_tag.h:166 at __alloc_tagging_slab_free_hook at allocation and free time respectively, as reported when reading files on a CIFS mount.  The allocations are also missing from /proc/allocinfo. Wrap the direct -&amp;gt;alloc() invocations in alloc_hooks() with a new mempool_alloc_noreserve() h…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98920</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4152 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, möglicherweise einen Denial-of-Service-Angriff auszulösen, Daten zu manipulieren oder offenzulegen oder Sicherheitsmaßnahmen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4152</guid>
    </item>
  </channel>
</rss>
