<?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-11-19T16:57:00.077516+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-2025-38488</id>
    <title>CVE-2025-38488 — smb: client: fix use-after-free in crypt_message when using async crypto</title>
    <updated>2026-11-19T16:57:00.158392+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>smb: client: fix use-after-free in crypt_message when using async crypto</p>
<p>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:</p>
<p>crypt_message()
    // Allocate the creq buffer containing the req
    creq = smb2_get_aead_req(..., &amp;req);</p>
<p>// Async encryption returns -EINPROGRESS immediately
    rc = enc ? crypto_aead_encrypt(req) : crypto_aead_decrypt(req);</p>
<p>// Free creq while async operation is still in progress
    kvfree_sensitive(creq, ...);</p>
<p>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.</p>
<p>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.</p>
<p>The issue occurs because crypto_alloc_aead() with mask=0 doesn't
guarantee synchronous operation. Even without CRYPTO_ALG_ASYNC in
the mask, async implementations can be selected.</p>
<p>Fix by restoring the async crypto handling:
- DECLARE_CRYPTO_WAIT(wait) for completion tracking
- aead_request_set_callb…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2025-38488"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/lsn-0118-1</id>
    <title>LSN-0118-1 — Kernel Live Patch Security Notice</title>
    <updated>2026-11-19T16:57:00.158506+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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.</p>
<p>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't marked with REQ_F_AS…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/lsn-0118-1"/>
  </entry>
</feed>
