<?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>Fri, 09 Oct 2026 17:27:48 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-98224</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-98224</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-98224</guid>
    </item>
    <item>
      <title>EUVD-2026-383336</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-383336</link>
      <description>EUVD-2026-383336</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-383336</guid>
    </item>
    <item>
      <title>fkie_cve-2026-98224</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-98224</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/vma: correctly unaccount on mmap_prepare() failure&lt;/p&gt;
&lt;p&gt;__mmap_setup() accounts memory for relevant mappings via:&lt;/p&gt;
&lt;p&gt;security_vm_enough_memory_mm()
  -&amp;gt; __vm_enough_memory()
    -&amp;gt; vm_acct_memory()&lt;/p&gt;
&lt;p&gt;If __mmap_setup() fails, this indicates that this accounting did not take
place, and thus it&amp;#39;s appropriate for __mmap_region() to jump to
abort_munmap.&lt;/p&gt;
&lt;p&gt;However if call_mmap_prepare() fails, it also jumps there and any accounted
memory is not correctly unaccounted.&lt;/p&gt;
&lt;p&gt;Fix this by handling each error separately.&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;mm/vma: correctly unaccount on mmap_prepare() failure&lt;/p&gt;
&lt;p&gt;__mmap_setup() accounts memory for relevant mappings via:&lt;/p&gt;
&lt;p&gt;security_vm_enough_memory_mm()
  -&amp;gt; __vm_enough_memory()
    -&amp;gt; vm_acct_memory()&lt;/p&gt;
&lt;p&gt;If __mmap_setup() fails, this indicates that this accounting did not take
place, and thus it&amp;#39;s appropriate for __mmap_region() to jump to
abort_munmap.&lt;/p&gt;
&lt;p&gt;However if call_mmap_prepare() fails, it also jumps there and any accounted
memory is not correctly unaccounted.&lt;/p&gt;
&lt;p&gt;Fix this by handling each error separately.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-98224</guid>
    </item>
    <item>
      <title>GHSA-mpjf-v662-xm2m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mpjf-v662-xm2m</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/vma: correctly unaccount on mmap_prepare() failure&lt;/p&gt;
&lt;p&gt;__mmap_setup() accounts memory for relevant mappings via:&lt;/p&gt;
&lt;p&gt;security_vm_enough_memory_mm()
  -&amp;gt; __vm_enough_memory()
    -&amp;gt; vm_acct_memory()&lt;/p&gt;
&lt;p&gt;If __mmap_setup() fails, this indicates that this accounting did not take
place, and thus it&amp;#39;s appropriate for __mmap_region() to jump to
abort_munmap.&lt;/p&gt;
&lt;p&gt;However if call_mmap_prepare() fails, it also jumps there and any accounted
memory is not correctly unaccounted.&lt;/p&gt;
&lt;p&gt;Fix this by handling each error separately.&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;mm/vma: correctly unaccount on mmap_prepare() failure&lt;/p&gt;
&lt;p&gt;__mmap_setup() accounts memory for relevant mappings via:&lt;/p&gt;
&lt;p&gt;security_vm_enough_memory_mm()
  -&amp;gt; __vm_enough_memory()
    -&amp;gt; vm_acct_memory()&lt;/p&gt;
&lt;p&gt;If __mmap_setup() fails, this indicates that this accounting did not take
place, and thus it&amp;#39;s appropriate for __mmap_region() to jump to
abort_munmap.&lt;/p&gt;
&lt;p&gt;However if call_mmap_prepare() fails, it also jumps there and any accounted
memory is not correctly unaccounted.&lt;/p&gt;
&lt;p&gt;Fix this by handling each error separately.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-mpjf-v662-xm2m</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-98224</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98224</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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/vma: correctly unaccount on mmap_prepare() failure __mmap_setup() accounts memory for relevant mappings via: security_vm_enough_memory_mm()   -&amp;gt; __vm_enough_memory()     -&amp;gt; vm_acct_memory() If __mmap_setup() fails, this indicates that this accounting did not take place, and thus it&amp;#39;s appropriate for __mmap_region() to jump to abort_munmap. However if call_mmap_prepare() fails, it also jumps there and any accounted memory is not correctly unaccounted. Fix this by handling each error separately.&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 120 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: mm/vma: correctly unaccount on mmap_prepare() failure __mmap_setup() accounts memory for relevant mappings via: security_vm_enough_memory_mm()   -&amp;gt; __vm_enough_memory()     -&amp;gt; vm_acct_memory() If __mmap_setup() fails, this indicates that this accounting did not take place, and thus it&amp;#39;s appropriate for __mmap_region() to jump to abort_munmap. However if call_mmap_prepare() fails, it also jumps there and any accounted memory is not correctly unaccounted. Fix this by handling each error separately.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-98224</guid>
    </item>
  </channel>
</rss>
