<?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://db.gcve.eu</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, 29 Oct 2026 12:03:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99098 — dm-integrity: fix buffer overflow in inline mode with large tag size</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99098</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 buffer overflow in inline mode with large tag size&lt;/p&gt;
&lt;p&gt;In inline mode, dm_integrity_check and dm_integrity_inline_recheck
compute the checksum of each block into an on-stack buffer of
HASH_MAX_DIGESTSIZE bytes. integrity_sector_checksum pads its result
with zeroes up to the tag size, so if the tag size is larger than
HASH_MAX_DIGESTSIZE, the padding runs past the end of the buffer. With
CONFIG_STACKPROTECTOR the kernel panics in dm_integrity_check on the
first read.&lt;/p&gt;
&lt;p&gt;Enlarge both buffers to hold MAX_TAG_SIZE bytes, as commit b93b6643e9b5
(&amp;#34;dm integrity: fix a crash with unusually large tag size&amp;#34;) did for
integrity_metadata.&lt;/p&gt;
&lt;p&gt;Note that this is not a security bug because the buffer overflow can only
be triggered by root.&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 buffer overflow in inline mode with large tag size&lt;/p&gt;
&lt;p&gt;In inline mode, dm_integrity_check and dm_integrity_inline_recheck
compute the checksum of each block into an on-stack buffer of
HASH_MAX_DIGESTSIZE bytes. integrity_sector_checksum pads its result
with zeroes up to the tag size, so if the tag size is larger than
HASH_MAX_DIGESTSIZE, the padding runs past the end of the buffer. With
CONFIG_STACKPROTECTOR the kernel panics in dm_integrity_check on the
first read.&lt;/p&gt;
&lt;p&gt;Enlarge both buffers to hold MAX_TAG_SIZE bytes, as commit b93b6643e9b5
(&amp;#34;dm integrity: fix a crash with unusually large tag size&amp;#34;) did for
integrity_metadata.&lt;/p&gt;
&lt;p&gt;Note that this is not a security bug because the buffer overflow can only
be triggered by root.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99098</guid>
    </item>
  </channel>
</rss>
