<?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:00:02 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-74671 — ima: fix out-of-bounds read in xattr_verify()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-74671</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;ima: fix out-of-bounds read in xattr_verify()&lt;/p&gt;
&lt;p&gt;The digest-length check in xattr_verify() mixes int and size_t:&lt;/p&gt;
&lt;p&gt;if (xattr_len - sizeof(xattr_value-&amp;gt;type) - hash_start &amp;gt;=
			iint-&amp;gt;ima_hash-&amp;gt;length)&lt;/p&gt;
&lt;p&gt;sizeof() yields size_t, so the usual arithmetic conversions promote
the whole left-hand side to unsigned 64-bit before the subtraction
runs. For a truncated xattr this underflows instead of going negative:
a 1-byte IMA_XATTR_DIGEST_NG xattr (xattr_len == 1, hash_start == 1)
turns &amp;#34;1 - 1 - 1&amp;#34; into SIZE_MAX, which is trivially &amp;gt;= ima_hash-&amp;gt;length.
The check then passes and the following memcmp() reads
iint-&amp;gt;ima_hash-&amp;gt;length bytes starting past the end of the buffer
vfs_getxattr_alloc() allocated for it.&lt;/p&gt;
&lt;p&gt;Nothing upstream clamps xattr_len back into a safe range first:
ima_get_hash_algo() only special-cases xattr_len &amp;lt; 2 to pick a default
algorithm, and evm_verifyxattr() returns INTEGRITY_UNKNOWN rather than
failing when no HMAC key is loaded, so a truncated security.ima value
reaches the length check as-is.&lt;/p&gt;
&lt;p&gt;Rewrite the comparison so every operand stays a signed int and no
implicit conversion to size_t can occur.&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;ima: fix out-of-bounds read in xattr_verify()&lt;/p&gt;
&lt;p&gt;The digest-length check in xattr_verify() mixes int and size_t:&lt;/p&gt;
&lt;p&gt;if (xattr_len - sizeof(xattr_value-&amp;gt;type) - hash_start &amp;gt;=
			iint-&amp;gt;ima_hash-&amp;gt;length)&lt;/p&gt;
&lt;p&gt;sizeof() yields size_t, so the usual arithmetic conversions promote
the whole left-hand side to unsigned 64-bit before the subtraction
runs. For a truncated xattr this underflows instead of going negative:
a 1-byte IMA_XATTR_DIGEST_NG xattr (xattr_len == 1, hash_start == 1)
turns &amp;#34;1 - 1 - 1&amp;#34; into SIZE_MAX, which is trivially &amp;gt;= ima_hash-&amp;gt;length.
The check then passes and the following memcmp() reads
iint-&amp;gt;ima_hash-&amp;gt;length bytes starting past the end of the buffer
vfs_getxattr_alloc() allocated for it.&lt;/p&gt;
&lt;p&gt;Nothing upstream clamps xattr_len back into a safe range first:
ima_get_hash_algo() only special-cases xattr_len &amp;lt; 2 to pick a default
algorithm, and evm_verifyxattr() returns INTEGRITY_UNKNOWN rather than
failing when no HMAC key is loaded, so a truncated security.ima value
reaches the length check as-is.&lt;/p&gt;
&lt;p&gt;Rewrite the comparison so every operand stays a signed int and no
implicit conversion to size_t can occur.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-74671</guid>
    </item>
  </channel>
</rss>
