<?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>Thu, 01 Oct 2026 11:04:21 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-46744 — Squashfs: sanity check symbolic link size</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-46744</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P, Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family, Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Squashfs: sanity check symbolic link size&lt;/p&gt;
&lt;p&gt;Syzkiller reports a &amp;#34;KMSAN: uninit-value in pick_link&amp;#34; bug.&lt;/p&gt;
&lt;p&gt;This is caused by an uninitialised page, which is ultimately caused
by a corrupted symbolic link size read from disk.&lt;/p&gt;
&lt;p&gt;The reason why the corrupted symlink size causes an uninitialised
page is due to the following sequence of events:&lt;/p&gt;
&lt;p&gt;1. squashfs_read_inode() is called to read the symbolic
   link from disk.  This assigns the corrupted value
   3875536935 to inode-&amp;gt;i_size.&lt;/p&gt;
&lt;p&gt;2. Later squashfs_symlink_read_folio() is called, which assigns
   this corrupted value to the length variable, which being a
   signed int, overflows producing a negative number.&lt;/p&gt;
&lt;p&gt;3. The following loop that fills in the page contents checks that
   the copied bytes is less than length, which being negative means
   the loop is skipped, producing an uninitialised page.&lt;/p&gt;
&lt;p&gt;This patch adds a sanity check which checks that the symbolic
link size is not larger than expected.&lt;/p&gt;
&lt;p&gt;--&lt;/p&gt;
&lt;p&gt;V2: fix spelling mistake.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Siemens RUGGEDCOM RST2428P, Siemens SCALANCE XC-300/XR-300/XC-400/XR-500WG/XR-500 family, Siemens SCALANCE XCM-/XRM-/XCH-/XRH-300 family, Siemens SIMATIC S7-1500 TM MFP - GNU/Linux subsystem&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;Squashfs: sanity check symbolic link size&lt;/p&gt;
&lt;p&gt;Syzkiller reports a &amp;#34;KMSAN: uninit-value in pick_link&amp;#34; bug.&lt;/p&gt;
&lt;p&gt;This is caused by an uninitialised page, which is ultimately caused
by a corrupted symbolic link size read from disk.&lt;/p&gt;
&lt;p&gt;The reason why the corrupted symlink size causes an uninitialised
page is due to the following sequence of events:&lt;/p&gt;
&lt;p&gt;1. squashfs_read_inode() is called to read the symbolic
   link from disk.  This assigns the corrupted value
   3875536935 to inode-&amp;gt;i_size.&lt;/p&gt;
&lt;p&gt;2. Later squashfs_symlink_read_folio() is called, which assigns
   this corrupted value to the length variable, which being a
   signed int, overflows producing a negative number.&lt;/p&gt;
&lt;p&gt;3. The following loop that fills in the page contents checks that
   the copied bytes is less than length, which being negative means
   the loop is skipped, producing an uninitialised page.&lt;/p&gt;
&lt;p&gt;This patch adds a sanity check which checks that the symbolic
link size is not larger than expected.&lt;/p&gt;
&lt;p&gt;--&lt;/p&gt;
&lt;p&gt;V2: fix spelling mistake.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-46744</guid>
    </item>
  </channel>
</rss>
