<?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://cve.radiocsirt.org</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, 07 Oct 2026 08:16:09 +0000</lastBuildDate>
    <item>
      <title>CVE-2022-49044 — dm integrity: fix memory corruption when tag_size is less than digest size</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2022-49044</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;dm integrity: fix memory corruption when tag_size is less than digest size&lt;/p&gt;
&lt;p&gt;It is possible to set up dm-integrity in such a way that the
&amp;#34;tag_size&amp;#34; parameter is less than the actual digest size. In this
situation, a part of the digest beyond tag_size is ignored.&lt;/p&gt;
&lt;p&gt;In this case, dm-integrity would write beyond the end of the
ic-&amp;gt;recalc_tags array and corrupt memory. The corruption happened in
integrity_recalc-&amp;gt;integrity_sector_checksum-&amp;gt;crypto_shash_final.&lt;/p&gt;
&lt;p&gt;Fix this corruption by increasing the tags array so that it has enough
padding at the end to accomodate the loop in integrity_recalc() being
able to write a full digest size for the last member of the tags
array.&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;dm integrity: fix memory corruption when tag_size is less than digest size&lt;/p&gt;
&lt;p&gt;It is possible to set up dm-integrity in such a way that the
&amp;#34;tag_size&amp;#34; parameter is less than the actual digest size. In this
situation, a part of the digest beyond tag_size is ignored.&lt;/p&gt;
&lt;p&gt;In this case, dm-integrity would write beyond the end of the
ic-&amp;gt;recalc_tags array and corrupt memory. The corruption happened in
integrity_recalc-&amp;gt;integrity_sector_checksum-&amp;gt;crypto_shash_final.&lt;/p&gt;
&lt;p&gt;Fix this corruption by increasing the tags array so that it has enough
padding at the end to accomodate the loop in integrity_recalc() being
able to write a full digest size for the last member of the tags
array.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2022-49044</guid>
    </item>
  </channel>
</rss>
