<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T08:22:59.365878+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2023-54050</id>
    <title>CVE-2023-54050 — ubifs: Fix memleak when insert_old_idx() failed</title>
    <updated>2026-10-04T08:22:59.367462+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: Fix memleak when insert_old_idx() failed</p>
<p>Following process will cause a memleak for copied up znode:</p>
<p>dirty_cow_znode
  zn = copy_znode(c, znode);
  err = insert_old_idx(c, zbr-&gt;lnum, zbr-&gt;offs);
  if (unlikely(err))
     return ERR_PTR(err);   // No one refers to zn.</p>
<p>Fetch a reproducer in [Link].</p>
<p>Function copy_znode() is split into 2 parts: resource allocation
and znode replacement, insert_old_idx() is split in similar way,
so resource cleanup could be done in error handling path without
corrupting metadata(mem &amp; disk).
It's okay that old index inserting is put behind of add_idx_dirt(),
old index is used in layout_leb_in_gaps(), so the two processes do
not depend on each other.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2023-54050"/>
  </entry>
</feed>
