<?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 22:35:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99136 — dm-crypt: fix a tiny race condition in crypt_dec_pending</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99136</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-crypt: fix a tiny race condition in crypt_dec_pending&lt;/p&gt;
&lt;p&gt;crypt_dec_pending reads io-&amp;gt;error before calling atomic_dec_and_test.
Another context, for example crypt_endio called from an interrupt, may
set io-&amp;gt;error and drop its reference between the read and the
decrement. crypt_dec_pending then drops the last reference and completes
the bio with the stale status - so a read that failed and was never
decrypted, or a write that failed, is reported as successful.&lt;/p&gt;
&lt;p&gt;The read was placed before the decrement by commit b35f8caa0890 (&amp;#34;dm
crypt: wait for endio to complete before destruction&amp;#34;), because that
commit freed dm_crypt_io before calling bio_endio. This is no longer the
case, dm_crypt_io lives in the per-bio data now.&lt;/p&gt;
&lt;p&gt;Read io-&amp;gt;error after atomic_dec_and_test instead. atomic_dec_and_test is
fully ordered, so no additional barrier is needed.&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-crypt: fix a tiny race condition in crypt_dec_pending&lt;/p&gt;
&lt;p&gt;crypt_dec_pending reads io-&amp;gt;error before calling atomic_dec_and_test.
Another context, for example crypt_endio called from an interrupt, may
set io-&amp;gt;error and drop its reference between the read and the
decrement. crypt_dec_pending then drops the last reference and completes
the bio with the stale status - so a read that failed and was never
decrypted, or a write that failed, is reported as successful.&lt;/p&gt;
&lt;p&gt;The read was placed before the decrement by commit b35f8caa0890 (&amp;#34;dm
crypt: wait for endio to complete before destruction&amp;#34;), because that
commit freed dm_crypt_io before calling bio_endio. This is no longer the
case, dm_crypt_io lives in the per-bio data now.&lt;/p&gt;
&lt;p&gt;Read io-&amp;gt;error after atomic_dec_and_test instead. atomic_dec_and_test is
fully ordered, so no additional barrier is needed.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99136</guid>
    </item>
  </channel>
</rss>
