<?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>Sat, 03 Oct 2026 08:17:31 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-39472 — xfs: fix log recovery buffer allocation for the legacy h_size fixup</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-39472</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;xfs: fix log recovery buffer allocation for the legacy h_size fixup&lt;/p&gt;
&lt;p&gt;Commit a70f9fe52daa (&amp;#34;xfs: detect and handle invalid iclog size set by
mkfs&amp;#34;) added a fixup for incorrect h_size values used for the initial
umount record in old xfsprogs versions.  Later commit 0c771b99d6c9
(&amp;#34;xfs: clean up calculation of LR header blocks&amp;#34;) cleaned up the log
reover buffer calculation, but stoped using the fixed up h_size value
to size the log recovery buffer, which can lead to an out of bounds
access when the incorrect h_size does not come from the old mkfs
tool, but a fuzzer.&lt;/p&gt;
&lt;p&gt;Fix this by open coding xlog_logrec_hblks and taking the fixed h_size
into account for this calculation.&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;xfs: fix log recovery buffer allocation for the legacy h_size fixup&lt;/p&gt;
&lt;p&gt;Commit a70f9fe52daa (&amp;#34;xfs: detect and handle invalid iclog size set by
mkfs&amp;#34;) added a fixup for incorrect h_size values used for the initial
umount record in old xfsprogs versions.  Later commit 0c771b99d6c9
(&amp;#34;xfs: clean up calculation of LR header blocks&amp;#34;) cleaned up the log
reover buffer calculation, but stoped using the fixed up h_size value
to size the log recovery buffer, which can lead to an out of bounds
access when the incorrect h_size does not come from the old mkfs
tool, but a fuzzer.&lt;/p&gt;
&lt;p&gt;Fix this by open coding xlog_logrec_hblks and taking the fixed h_size
into account for this calculation.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-39472</guid>
    </item>
  </channel>
</rss>
