<?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, 19 Nov 2026 16:56:59 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-38488 — smb: client: fix use-after-free in crypt_message when using async crypto</title>
      <link>https://db.gcve.eu/vuln/cve-2025-38488</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;smb: client: fix use-after-free in crypt_message when using async crypto&lt;/p&gt;
&lt;p&gt;The CVE-2024-50047 fix removed asynchronous crypto handling from
crypt_message(), assuming all crypto operations are synchronous.
However, when hardware crypto accelerators are used, this can cause
use-after-free crashes:&lt;/p&gt;
&lt;p&gt;crypt_message()
    // Allocate the creq buffer containing the req
    creq = smb2_get_aead_req(..., &amp;amp;req);&lt;/p&gt;
&lt;p&gt;// Async encryption returns -EINPROGRESS immediately
    rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);&lt;/p&gt;
&lt;p&gt;// Free creq while async operation is still in progress
    kvfree_sensitive(creq, ...);&lt;/p&gt;
&lt;p&gt;Hardware crypto modules often implement async AEAD operations for
performance. When crypto_aead_encrypt/decrypt() returns -EINPROGRESS,
the operation completes asynchronously. Without crypto_wait_req(),
the function immediately frees the request buffer, leading to crashes
when the driver later accesses the freed memory.&lt;/p&gt;
&lt;p&gt;This results in a use-after-free condition when the hardware crypto
driver later accesses the freed request structure, leading to kernel
crashes with NULL pointer dereferences.&lt;/p&gt;
&lt;p&gt;The issue occurs because crypto_alloc_aead() with mask=0 doesn&amp;#39;t
guarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in
the mask, async implementations can be selected.&lt;/p&gt;
&lt;p&gt;Fix by restoring the async crypto handling:
- DECLARE_CRYPTO_WAIT(wait) for completion tracking
- aead_request_set_callb…&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;smb: client: fix use-after-free in crypt_message when using async crypto&lt;/p&gt;
&lt;p&gt;The CVE-2024-50047 fix removed asynchronous crypto handling from
crypt_message(), assuming all crypto operations are synchronous.
However, when hardware crypto accelerators are used, this can cause
use-after-free crashes:&lt;/p&gt;
&lt;p&gt;crypt_message()
    // Allocate the creq buffer containing the req
    creq = smb2_get_aead_req(..., &amp;amp;req);&lt;/p&gt;
&lt;p&gt;// Async encryption returns -EINPROGRESS immediately
    rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);&lt;/p&gt;
&lt;p&gt;// Free creq while async operation is still in progress
    kvfree_sensitive(creq, ...);&lt;/p&gt;
&lt;p&gt;Hardware crypto modules often implement async AEAD operations for
performance. When crypto_aead_encrypt/decrypt() returns -EINPROGRESS,
the operation completes asynchronously. Without crypto_wait_req(),
the function immediately frees the request buffer, leading to crashes
when the driver later accesses the freed memory.&lt;/p&gt;
&lt;p&gt;This results in a use-after-free condition when the hardware crypto
driver later accesses the freed request structure, leading to kernel
crashes with NULL pointer dereferences.&lt;/p&gt;
&lt;p&gt;The issue occurs because crypto_alloc_aead() with mask=0 doesn&amp;#39;t
guarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in
the mask, async implementations can be selected.&lt;/p&gt;
&lt;p&gt;Fix by restoring the async crypto handling:
- DECLARE_CRYPTO_WAIT(wait) for completion tracking
- aead_request_set_callb…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2025-38488</guid>
    </item>
    <item>
      <title>LSN-0118-1 — Kernel Live Patch Security Notice</title>
      <link>https://db.gcve.eu/vuln/lsn-0118-1</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-aws, Ubuntu:Pro:20.04:LTS: linux-azure-5.15, Ubuntu:Pro:20.04:LTS: linux-gcp-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-oracle-5.15 and 17 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: smb: client: fix UAF in async decryption Doing an async
decryption (large read) crashes with a slab-use-after-free way down in the
crypto API.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: padata: avoid UAF for reorder_work Although the previous patch
can avoid ps and ps UAF for _do_serial, it can not avoid potential UAF
issue for reorder_work.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: exfat: fix random stack corruption after get_block When get_block
is called with a buffer_head allocated on the stack, such as
do_mpage_readpage, stack corruption due to buffer_head UAF may occur in the
following race condition situation.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: smb: client: fix use-after-free in crypt_message when using async
crypto The CVE-2024-50047 fix removed asynchronous crypto handling from
crypt_message(), assuming all crypto operations are synchronous.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: ksmbd: fix Preauh_HashValue race condition If client send
multiple session setup requests to ksmbd, Preauh_HashValue race condition
could happen.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: io_uring/futex: ensure io_futex_wait() cleans up properly on
failure The io_futex_data is allocated upfront and assigned to the io_kiocb
async_data field, but the request isn&amp;#39;t marked with REQ_F_AS…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:18.04:LTS: linux-hwe-5.4, Ubuntu:Pro:20.04:LTS: linux-aws-5.15, Ubuntu:Pro:20.04:LTS: linux-aws, Ubuntu:Pro:20.04:LTS: linux-azure-5.15, Ubuntu:Pro:20.04:LTS: linux-gcp-5.15, Ubuntu:Pro:20.04:LTS: linux-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux-lowlatency-hwe-5.15, Ubuntu:Pro:20.04:LTS: linux, Ubuntu:Pro:20.04:LTS: linux-ibm-5.15, Ubuntu:Pro:20.04:LTS: linux-oracle-5.15 and 17 more&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: smb: client: fix UAF in async decryption Doing an async
decryption (large read) crashes with a slab-use-after-free way down in the
crypto API.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: padata: avoid UAF for reorder_work Although the previous patch
can avoid ps and ps UAF for _do_serial, it can not avoid potential UAF
issue for reorder_work.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: exfat: fix random stack corruption after get_block When get_block
is called with a buffer_head allocated on the stack, such as
do_mpage_readpage, stack corruption due to buffer_head UAF may occur in the
following race condition situation.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: smb: client: fix use-after-free in crypt_message when using async
crypto The CVE-2024-50047 fix removed asynchronous crypto handling from
crypt_message(), assuming all crypto operations are synchronous.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: ksmbd: fix Preauh_HashValue race condition If client send
multiple session setup requests to ksmbd, Preauh_HashValue race condition
could happen.&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been
resolved: io_uring/futex: ensure io_futex_wait() cleans up properly on
failure The io_futex_data is allocated upfront and assigned to the io_kiocb
async_data field, but the request isn&amp;#39;t marked with REQ_F_AS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/lsn-0118-1</guid>
    </item>
  </channel>
</rss>
