<?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>Wed, 30 Sep 2026 16:23:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-41014 — xfs: add bounds checking to xlog_recover_process_data</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-41014</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: add bounds checking to xlog_recover_process_data&lt;/p&gt;
&lt;p&gt;There is a lack of verification of the space occupied by fixed members
of xlog_op_header in the xlog_recover_process_data.&lt;/p&gt;
&lt;p&gt;We can create a crafted image to trigger an out of bounds read by
following these steps:
    1) Mount an image of xfs, and do some file operations to leave records
    2) Before umounting, copy the image for subsequent steps to simulate
       abnormal exit. Because umount will ensure that tail_blk and
       head_blk are the same, which will result in the inability to enter
       xlog_recover_process_data
    3) Write a tool to parse and modify the copied image in step 2
    4) Make the end of the xlog_op_header entries only 1 byte away from
       xlog_rec_header-&amp;gt;h_size
    5) xlog_rec_header-&amp;gt;h_num_logops++
    6) Modify xlog_rec_header-&amp;gt;h_crc&lt;/p&gt;
&lt;p&gt;Fix:
Add a check to make sure there is sufficient space to access fixed members
of xlog_op_header.&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: add bounds checking to xlog_recover_process_data&lt;/p&gt;
&lt;p&gt;There is a lack of verification of the space occupied by fixed members
of xlog_op_header in the xlog_recover_process_data.&lt;/p&gt;
&lt;p&gt;We can create a crafted image to trigger an out of bounds read by
following these steps:
    1) Mount an image of xfs, and do some file operations to leave records
    2) Before umounting, copy the image for subsequent steps to simulate
       abnormal exit. Because umount will ensure that tail_blk and
       head_blk are the same, which will result in the inability to enter
       xlog_recover_process_data
    3) Write a tool to parse and modify the copied image in step 2
    4) Make the end of the xlog_op_header entries only 1 byte away from
       xlog_rec_header-&amp;gt;h_size
    5) xlog_rec_header-&amp;gt;h_num_logops++
    6) Modify xlog_rec_header-&amp;gt;h_crc&lt;/p&gt;
&lt;p&gt;Fix:
Add a check to make sure there is sufficient space to access fixed members
of xlog_op_header.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-41014</guid>
    </item>
  </channel>
</rss>
