<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-29T23:26:53.597709+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-99136</id>
    <title>CVE-2026-99136 — dm-crypt: fix a tiny race condition in crypt_dec_pending</title>
    <updated>2026-10-29T23:26:53.600534+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>dm-crypt: fix a tiny race condition in crypt_dec_pending</p>
<p>crypt_dec_pending reads io-&gt;error before calling atomic_dec_and_test.
Another context, for example crypt_endio called from an interrupt, may
set io-&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.</p>
<p>The read was placed before the decrement by commit b35f8caa0890 ("dm
crypt: wait for endio to complete before destruction"), 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.</p>
<p>Read io-&gt;error after atomic_dec_and_test instead. atomic_dec_and_test is
fully ordered, so no additional barrier is needed.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-99136"/>
  </entry>
</feed>
