<?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>Wed, 07 Oct 2026 08:24:09 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-04391</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-04391</link>
      <description>bdu:2026-04391</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-04391</guid>
    </item>
    <item>
      <title>BELL-CVE-2024-42293</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2024-42293</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-2024-42293</guid>
    </item>
    <item>
      <title>EUVD-2026-346004</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-346004</link>
      <description>EUVD-2026-346004</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-346004</guid>
    </item>
    <item>
      <title>fkie_cve-2024-42293</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-42293</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64: mm: Fix lockless walks with static and dynamic page-table folding&lt;/p&gt;
&lt;p&gt;Lina reports random oopsen originating from the fast GUP code when
16K pages are used with 4-level page-tables, the fourth level being
folded at runtime due to lack of LPA2.&lt;/p&gt;
&lt;p&gt;In this configuration, the generic implementation of
p4d_offset_lockless() will return a &amp;#39;p4d_t *&amp;#39; corresponding to the
&amp;#39;pgd_t&amp;#39; allocated on the stack of the caller, gup_fast_pgd_range().
This is normally fine, but when the fourth level of page-table is folded
at runtime, pud_offset_lockless() will offset from the address of the
&amp;#39;p4d_t&amp;#39; to calculate the address of the PUD in the same page-table page.
This results in a stray stack read when the &amp;#39;p4d_t&amp;#39; has been allocated
on the stack and can send the walker into the weeds.&lt;/p&gt;
&lt;p&gt;Fix the problem by providing our own definition of p4d_offset_lockless()
when CONFIG_PGTABLE_LEVELS &amp;lt;= 4 which returns the real page-table
pointer rather than the address of the local stack variable.&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;arm64: mm: Fix lockless walks with static and dynamic page-table folding&lt;/p&gt;
&lt;p&gt;Lina reports random oopsen originating from the fast GUP code when
16K pages are used with 4-level page-tables, the fourth level being
folded at runtime due to lack of LPA2.&lt;/p&gt;
&lt;p&gt;In this configuration, the generic implementation of
p4d_offset_lockless() will return a &amp;#39;p4d_t *&amp;#39; corresponding to the
&amp;#39;pgd_t&amp;#39; allocated on the stack of the caller, gup_fast_pgd_range().
This is normally fine, but when the fourth level of page-table is folded
at runtime, pud_offset_lockless() will offset from the address of the
&amp;#39;p4d_t&amp;#39; to calculate the address of the PUD in the same page-table page.
This results in a stray stack read when the &amp;#39;p4d_t&amp;#39; has been allocated
on the stack and can send the walker into the weeds.&lt;/p&gt;
&lt;p&gt;Fix the problem by providing our own definition of p4d_offset_lockless()
when CONFIG_PGTABLE_LEVELS &amp;lt;= 4 which returns the real page-table
pointer rather than the address of the local stack variable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-42293</guid>
    </item>
    <item>
      <title>GHSA-h48v-q4mj-95wg</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-h48v-q4mj-95wg</link>
      <description>&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;arm64: mm: Fix lockless walks with static and dynamic page-table folding&lt;/p&gt;
&lt;p&gt;Lina reports random oopsen originating from the fast GUP code when
16K pages are used with 4-level page-tables, the fourth level being
folded at runtime due to lack of LPA2.&lt;/p&gt;
&lt;p&gt;In this configuration, the generic implementation of
p4d_offset_lockless() will return a &amp;#39;p4d_t *&amp;#39; corresponding to the
&amp;#39;pgd_t&amp;#39; allocated on the stack of the caller, gup_fast_pgd_range().
This is normally fine, but when the fourth level of page-table is folded
at runtime, pud_offset_lockless() will offset from the address of the
&amp;#39;p4d_t&amp;#39; to calculate the address of the PUD in the same page-table page.
This results in a stray stack read when the &amp;#39;p4d_t&amp;#39; has been allocated
on the stack and can send the walker into the weeds.&lt;/p&gt;
&lt;p&gt;Fix the problem by providing our own definition of p4d_offset_lockless()
when CONFIG_PGTABLE_LEVELS &amp;lt;= 4 which returns the real page-table
pointer rather than the address of the local stack variable.&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;arm64: mm: Fix lockless walks with static and dynamic page-table folding&lt;/p&gt;
&lt;p&gt;Lina reports random oopsen originating from the fast GUP code when
16K pages are used with 4-level page-tables, the fourth level being
folded at runtime due to lack of LPA2.&lt;/p&gt;
&lt;p&gt;In this configuration, the generic implementation of
p4d_offset_lockless() will return a &amp;#39;p4d_t *&amp;#39; corresponding to the
&amp;#39;pgd_t&amp;#39; allocated on the stack of the caller, gup_fast_pgd_range().
This is normally fine, but when the fourth level of page-table is folded
at runtime, pud_offset_lockless() will offset from the address of the
&amp;#39;p4d_t&amp;#39; to calculate the address of the PUD in the same page-table page.
This results in a stray stack read when the &amp;#39;p4d_t&amp;#39; has been allocated
on the stack and can send the walker into the weeds.&lt;/p&gt;
&lt;p&gt;Fix the problem by providing our own definition of p4d_offset_lockless()
when CONFIG_PGTABLE_LEVELS &amp;lt;= 4 which returns the real page-table
pointer rather than the address of the local stack variable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-h48v-q4mj-95wg</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2024-42293</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-42293</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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: mm: Fix lockless walks with static and dynamic page-table folding Lina reports random oopsen originating from the fast GUP code when 16K pages are used with 4-level page-tables, the fourth level being folded at runtime due to lack of LPA2. In this configuration, the generic implementation of p4d_offset_lockless() will return a &amp;#39;p4d_t *&amp;#39; corresponding to the &amp;#39;pgd_t&amp;#39; allocated on the stack of the caller, gup_fast_pgd_range(). This is normally fine, but when the fourth level of page-table is folded at runtime, pud_offset_lockless() will offset from the address of the &amp;#39;p4d_t&amp;#39; to calculate the address of the PUD in the same page-table page. This results in a stray stack read when the &amp;#39;p4d_t&amp;#39; has been allocated on the stack and can send the walker into the weeds. Fix the problem by providing our own definition of p4d_offset_lockless() when CONFIG_PGTABLE_LEVELS &amp;lt;= 4 which returns the real page-table pointer rather than the address of the local stack variable.&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 66 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved: arm64: mm: Fix lockless walks with static and dynamic page-table folding Lina reports random oopsen originating from the fast GUP code when 16K pages are used with 4-level page-tables, the fourth level being folded at runtime due to lack of LPA2. In this configuration, the generic implementation of p4d_offset_lockless() will return a &amp;#39;p4d_t *&amp;#39; corresponding to the &amp;#39;pgd_t&amp;#39; allocated on the stack of the caller, gup_fast_pgd_range(). This is normally fine, but when the fourth level of page-table is folded at runtime, pud_offset_lockless() will offset from the address of the &amp;#39;p4d_t&amp;#39; to calculate the address of the PUD in the same page-table page. This results in a stray stack read when the &amp;#39;p4d_t&amp;#39; has been allocated on the stack and can send the walker into the weeds. Fix the problem by providing our own definition of p4d_offset_lockless() when CONFIG_PGTABLE_LEVELS &amp;lt;= 4 which returns the real page-table pointer rather than the address of the local stack variable.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2024-42293</guid>
    </item>
    <item>
      <title>WID-SEC-W-2024-1875 — Linux Kernel: Mehrere Schwachstellen ermöglichen Denial of Service</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1875</link>
      <description>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu erzielen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein lokaler Angreifer kann mehrere Schwachstellen in Linux Kernel ausnutzen, um einen Denial of Service Angriff durchzuführen oder unbekannte Auswirkungen zu erzielen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2024-1875</guid>
    </item>
  </channel>
</rss>
