<?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>Sun, 04 Oct 2026 00:52:56 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80685</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-80685</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:25: linux-lts, Alpaquita:stream: linux-lts&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-80685</guid>
    </item>
    <item>
      <title>EUVD-2026-372819</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-372819</link>
      <description>EUVD-2026-372819</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-372819</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80685</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-80685</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/util: don&amp;#39;t read __page_2 for order-1 folios in snapshot_page()&lt;/p&gt;
&lt;p&gt;snapshot_page() currently reads __page_2 after checking nr_pages &amp;gt; 1, but
it should only do so when nr_pages &amp;gt; 2.&lt;/p&gt;
&lt;p&gt;If an order-1 folio is allocated at the end of a vmemmap section,
__page_2 will not exist and reading it will cause a fault.&lt;/p&gt;
&lt;p&gt;During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed
on the page isolation path while reading an order-1 folio&amp;#39;s __page_2 from
an adjacent absent section (unmapped vmemmap).&lt;/p&gt;
&lt;p&gt;Fix this to avoid reading memmap that doesn&amp;#39;t exist (e.g., a vmemmap
hole).&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/util: don&amp;#39;t read __page_2 for order-1 folios in snapshot_page()&lt;/p&gt;
&lt;p&gt;snapshot_page() currently reads __page_2 after checking nr_pages &amp;gt; 1, but
it should only do so when nr_pages &amp;gt; 2.&lt;/p&gt;
&lt;p&gt;If an order-1 folio is allocated at the end of a vmemmap section,
__page_2 will not exist and reading it will cause a fault.&lt;/p&gt;
&lt;p&gt;During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed
on the page isolation path while reading an order-1 folio&amp;#39;s __page_2 from
an adjacent absent section (unmapped vmemmap).&lt;/p&gt;
&lt;p&gt;Fix this to avoid reading memmap that doesn&amp;#39;t exist (e.g., a vmemmap
hole).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-80685</guid>
    </item>
    <item>
      <title>GHSA-ccm4-344c-hjv9</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-ccm4-344c-hjv9</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;mm/util: don&amp;#39;t read __page_2 for order-1 folios in snapshot_page()&lt;/p&gt;
&lt;p&gt;snapshot_page() currently reads __page_2 after checking nr_pages &amp;gt; 1, but
it should only do so when nr_pages &amp;gt; 2.&lt;/p&gt;
&lt;p&gt;If an order-1 folio is allocated at the end of a vmemmap section,
__page_2 will not exist and reading it will cause a fault.&lt;/p&gt;
&lt;p&gt;During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed
on the page isolation path while reading an order-1 folio&amp;#39;s __page_2 from
an adjacent absent section (unmapped vmemmap).&lt;/p&gt;
&lt;p&gt;Fix this to avoid reading memmap that doesn&amp;#39;t exist (e.g., a vmemmap
hole).&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/util: don&amp;#39;t read __page_2 for order-1 folios in snapshot_page()&lt;/p&gt;
&lt;p&gt;snapshot_page() currently reads __page_2 after checking nr_pages &amp;gt; 1, but
it should only do so when nr_pages &amp;gt; 2.&lt;/p&gt;
&lt;p&gt;If an order-1 folio is allocated at the end of a vmemmap section,
__page_2 will not exist and reading it will cause a fault.&lt;/p&gt;
&lt;p&gt;During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed
on the page isolation path while reading an order-1 folio&amp;#39;s __page_2 from
an adjacent absent section (unmapped vmemmap).&lt;/p&gt;
&lt;p&gt;Fix this to avoid reading memmap that doesn&amp;#39;t exist (e.g., a vmemmap
hole).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-ccm4-344c-hjv9</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80685</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80685</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/util: don&amp;#39;t read __page_2 for order-1 folios in snapshot_page() snapshot_page() currently reads __page_2 after checking nr_pages &amp;gt; 1, but it should only do so when nr_pages &amp;gt; 2. If an order-1 folio is allocated at the end of a vmemmap section, __page_2 will not exist and reading it will cause a fault. During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed on the page isolation path while reading an order-1 folio&amp;#39;s __page_2 from an adjacent absent section (unmapped vmemmap). Fix this to avoid reading memmap that doesn&amp;#39;t exist (e.g., a vmemmap hole).&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/util: don&amp;#39;t read __page_2 for order-1 folios in snapshot_page() snapshot_page() currently reads __page_2 after checking nr_pages &amp;gt; 1, but it should only do so when nr_pages &amp;gt; 2. If an order-1 folio is allocated at the end of a vmemmap section, __page_2 will not exist and reading it will cause a fault. During DLPAR memory remove on a 22 TB ppc64le LPAR, snapshot_page() oopsed on the page isolation path while reading an order-1 folio&amp;#39;s __page_2 from an adjacent absent section (unmapped vmemmap). Fix this to avoid reading memmap that doesn&amp;#39;t exist (e.g., a vmemmap hole).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-80685</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-3075 — Linux Kernel: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen im Linux Kernel ausnutzen, um einen nicht näher spezifizierten Angriff durchzuführen, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&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, darunter möglicherweise Speicherbeschädigungen, die Offenlegung oder Manipulation von Daten sowie Denial-of-Service-Zustände.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-3075</guid>
    </item>
  </channel>
</rss>
