<?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>Fri, 02 Oct 2026 04:24:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-44965 — x86/mm: Fix pti_clone_pgtable() alignment assumption</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-44965</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;x86/mm: Fix pti_clone_pgtable() alignment assumption&lt;/p&gt;
&lt;p&gt;Guenter reported dodgy crashes on an i386-nosmp build using GCC-11
that had the form of endless traps until entry stack exhaust and then
#DF from the stack guard.&lt;/p&gt;
&lt;p&gt;It turned out that pti_clone_pgtable() had alignment assumptions on
the start address, notably it hard assumes start is PMD aligned. This
is true on x86_64, but very much not true on i386.&lt;/p&gt;
&lt;p&gt;These assumptions can cause the end condition to malfunction, leading
to a &amp;#39;short&amp;#39; clone. Guess what happens when the user mapping has a
short copy of the entry text?&lt;/p&gt;
&lt;p&gt;Use the correct increment form for addr to avoid alignment
assumptions.&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;x86/mm: Fix pti_clone_pgtable() alignment assumption&lt;/p&gt;
&lt;p&gt;Guenter reported dodgy crashes on an i386-nosmp build using GCC-11
that had the form of endless traps until entry stack exhaust and then
#DF from the stack guard.&lt;/p&gt;
&lt;p&gt;It turned out that pti_clone_pgtable() had alignment assumptions on
the start address, notably it hard assumes start is PMD aligned. This
is true on x86_64, but very much not true on i386.&lt;/p&gt;
&lt;p&gt;These assumptions can cause the end condition to malfunction, leading
to a &amp;#39;short&amp;#39; clone. Guess what happens when the user mapping has a
short copy of the entry text?&lt;/p&gt;
&lt;p&gt;Use the correct increment form for addr to avoid alignment
assumptions.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-44965</guid>
    </item>
  </channel>
</rss>
