<?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-19T17:52:55.796175+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-2024-53171</id>
    <title>CVE-2024-53171 — ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit</title>
    <updated>2026-11-19T17:52:56.137917+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>ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit</p>
<p>After an insertion in TNC, the tree might split and cause a node to
change its `znode-&gt;parent`. A further deletion of other nodes in the
tree (which also could free the nodes), the aforementioned node's
`znode-&gt;cparent` could still point to a freed node. This
`znode-&gt;cparent` may not be updated when getting nodes to commit in
`ubifs_tnc_start_commit()`. This could then trigger a use-after-free
when accessing the `znode-&gt;cparent` in `write_index()` in
`ubifs_tnc_end_commit()`.</p>
<p>This can be triggered by running</p>
<p>rm -f /etc/test-file.bin
  dd if=/dev/urandom of=/etc/test-file.bin bs=1M count=60 conv=fsync</p>
<p>in a loop, and with `CONFIG_UBIFS_FS_AUTHENTICATION`. KASAN then
reports:</p>
<p>BUG: KASAN: use-after-free in ubifs_tnc_end_commit+0xa5c/0x1950
  Write of size 32 at addr ffffff800a3af86c by task ubifs_bgt0_20/153</p>
<p>Call trace:
   dump_backtrace+0x0/0x340
   show_stack+0x18/0x24
   dump_stack_lvl+0x9c/0xbc
   print_address_description.constprop.0+0x74/0x2b0
   kasan_report+0x1d8/0x1f0
   kasan_check_range+0xf8/0x1a0
   memcpy+0x84/0xf4
   ubifs_tnc_end_commit+0xa5c/0x1950
   do_commit+0x4e0/0x1340
   ubifs_bg_thread+0x234/0x2e0
   kthread+0x36c/0x410
   ret_from_fork+0x10/0x20</p>
<p>Allocated by task 401:
   kasan_save_stack+0x38/0x70
   __kasan_kmalloc+0x8c/0xd0
   __kmalloc+0x34c/0x5bc
   tnc_insert+0x140/0x16a4
   ubifs_tnc_add+0x370/0x52c…</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2024-53171"/>
  </entry>
  <entry>
    <id>https://db.gcve.eu/vuln/lsn-0113-1</id>
    <title>LSN-0113-1 — Kernel Live Patch Security Notice</title>
    <updated>2026-11-19T17:52:56.138051+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:Pro:14.04:LTS: linux-lts-xenial, Ubuntu:Pro:16.04:LTS: linux-aws-hwe, Ubuntu:Pro:16.04:LTS: linux-aws, Ubuntu:Pro:16.04:LTS: linux-azure, Ubuntu:Pro:16.04:LTS: linux-gcp, Ubuntu:Pro:16.04:LTS: linux-hwe, Ubuntu:Pro:16.04:LTS: linux, Ubuntu:Pro:18.04:LTS: linux-aws, Ubuntu:Pro:18.04:LTS: linux-azure-4.15, Ubuntu:Pro:18.04:LTS: linux-gcp-4.15 and 30 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: ubifs: authentication: Fix use-after-free in ubifs_tnc_end_commit
After an insertion in TNC, the tree might split and cause a node to change
its `znode-&gt;parent`.</p>
<p>In the Linux kernel, the following vulnerability has been
resolved: drm/amdgpu: fix usage slab after free</p>
<p>In the Linux kernel, the following vulnerability has been
resolved: jfs: fix array-index-out-of-bounds in jfs_readdir The stbl might
contain some invalid values.</p>
<p>In the Linux kernel, the following vulnerability has been
resolved: drm/amd/display: Fix out-of-bounds access in
'dcn21_link_encoder_create' An issue was identified in the
dcn21_link_encoder_create function where an out-of-bounds access could
occur when the hpd_source index was used to reference the link_enc_hpd_regs
array.</p>
<p>In the Linux kernel, the following vulnerability has been
resolved: jffs2: Prevent rtime decompress memory corruption The rtime
decompression routine does not fully check bounds during the entirety of
the decompression pass and can corrupt memory outside the decompression
buffer if the compressed data is corrupted.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/lsn-0113-1"/>
  </entry>
</feed>
