[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2025122424-CVE-2023-54050-737a@gregkh>
Date: Wed, 24 Dec 2025 13:26:43 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-54050: ubifs: Fix memleak when insert_old_idx() failed
From: Greg Kroah-Hartman <gregkh@...nel.org>
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
ubifs: Fix memleak when insert_old_idx() failed
Following process will cause a memleak for copied up znode:
dirty_cow_znode
zn = copy_znode(c, znode);
err = insert_old_idx(c, zbr->lnum, zbr->offs);
if (unlikely(err))
return ERR_PTR(err); // No one refers to zn.
Fetch a reproducer in [Link].
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 & 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.
The Linux kernel CVE team has assigned CVE-2023-54050 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.27 with commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d and fixed in 4.19.283 with commit cc29c7216d7f057eb0613b97dc38c7e1962a88d2
Issue introduced in 2.6.27 with commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d and fixed in 5.4.243 with commit 6f2eee5457bc48b0426dedfd78cdbdea241a6edb
Issue introduced in 2.6.27 with commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d and fixed in 5.10.180 with commit 66e9f2fb3e753f820bec2a98e8c6387029988320
Issue introduced in 2.6.27 with commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d and fixed in 5.15.111 with commit 3ae75f82c33fa1b4ca2006b55c84f4ef4a428d4d
Issue introduced in 2.6.27 with commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d and fixed in 6.1.28 with commit ef9aac603659e9ffe7d69ae16e3f0fc0991a965b
Issue introduced in 2.6.27 with commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d and fixed in 6.2.15 with commit 79079cebbeed624b9d01cfcf1e3254ae1a1f6e14
Issue introduced in 2.6.27 with commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d and fixed in 6.3.2 with commit a6da0ab9847779e05a7416c7a98148b549de69ef
Issue introduced in 2.6.27 with commit 1e51764a3c2ac05a23a22b2a95ddee4d9bffb16d and fixed in 6.4 with commit b5fda08ef213352ac2df7447611eb4d383cce929
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2023-54050
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
fs/ubifs/tnc.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/cc29c7216d7f057eb0613b97dc38c7e1962a88d2
https://git.kernel.org/stable/c/6f2eee5457bc48b0426dedfd78cdbdea241a6edb
https://git.kernel.org/stable/c/66e9f2fb3e753f820bec2a98e8c6387029988320
https://git.kernel.org/stable/c/3ae75f82c33fa1b4ca2006b55c84f4ef4a428d4d
https://git.kernel.org/stable/c/ef9aac603659e9ffe7d69ae16e3f0fc0991a965b
https://git.kernel.org/stable/c/79079cebbeed624b9d01cfcf1e3254ae1a1f6e14
https://git.kernel.org/stable/c/a6da0ab9847779e05a7416c7a98148b549de69ef
https://git.kernel.org/stable/c/b5fda08ef213352ac2df7447611eb4d383cce929
Powered by blists - more mailing lists