<?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>Thu, 01 Oct 2026 22:08:13 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-31719 — crypto: krb5enc - fix async decrypt skipping hash verification</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-31719</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;crypto: krb5enc - fix async decrypt skipping hash verification&lt;/p&gt;
&lt;p&gt;krb5enc_dispatch_decrypt() sets req-&amp;gt;base.complete as the skcipher
callback, which is the caller&amp;#39;s own completion handler. When the
skcipher completes asynchronously, this signals &amp;#34;done&amp;#34; to the caller
without executing krb5enc_dispatch_decrypt_hash(), completely bypassing
the integrity verification (hash check).&lt;/p&gt;
&lt;p&gt;Compare with the encrypt path which correctly uses
krb5enc_encrypt_done as an intermediate callback to chain into the
hash computation on async completion.&lt;/p&gt;
&lt;p&gt;Fix by adding krb5enc_decrypt_done as an intermediate callback that
chains into krb5enc_dispatch_decrypt_hash() upon async skcipher
completion, matching the encrypt path&amp;#39;s callback pattern.&lt;/p&gt;
&lt;p&gt;Also fix EBUSY/EINPROGRESS handling throughout: remove
krb5enc_request_complete() which incorrectly swallowed EINPROGRESS
notifications that must be passed up to callers waiting on backlogged
requests, and add missing EBUSY checks in krb5enc_encrypt_ahash_done
for the dispatch_encrypt return value.&lt;/p&gt;
&lt;p&gt;Unset MAY_BACKLOG on the async completion path so the user won&amp;#39;t
see back-to-back EINPROGRESS notifications.&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;crypto: krb5enc - fix async decrypt skipping hash verification&lt;/p&gt;
&lt;p&gt;krb5enc_dispatch_decrypt() sets req-&amp;gt;base.complete as the skcipher
callback, which is the caller&amp;#39;s own completion handler. When the
skcipher completes asynchronously, this signals &amp;#34;done&amp;#34; to the caller
without executing krb5enc_dispatch_decrypt_hash(), completely bypassing
the integrity verification (hash check).&lt;/p&gt;
&lt;p&gt;Compare with the encrypt path which correctly uses
krb5enc_encrypt_done as an intermediate callback to chain into the
hash computation on async completion.&lt;/p&gt;
&lt;p&gt;Fix by adding krb5enc_decrypt_done as an intermediate callback that
chains into krb5enc_dispatch_decrypt_hash() upon async skcipher
completion, matching the encrypt path&amp;#39;s callback pattern.&lt;/p&gt;
&lt;p&gt;Also fix EBUSY/EINPROGRESS handling throughout: remove
krb5enc_request_complete() which incorrectly swallowed EINPROGRESS
notifications that must be passed up to callers waiting on backlogged
requests, and add missing EBUSY checks in krb5enc_encrypt_ahash_done
for the dispatch_encrypt return value.&lt;/p&gt;
&lt;p&gt;Unset MAY_BACKLOG on the async completion path so the user won&amp;#39;t
see back-to-back EINPROGRESS notifications.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-31719</guid>
    </item>
  </channel>
</rss>
