linux-cve-announce - CVE-2023-53396: ubifs: Fix memory leak in do

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <2025091859-CVE-2023-53396-27d9@gregkh>
Date: Thu, 18 Sep 2025 15:34:41 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...nel.org>
Subject: CVE-2023-53396: ubifs: Fix memory leak in do_rename

From: Greg Kroah-Hartman <gregkh@...nel.org>

Description
===========

In the Linux kernel, the following vulnerability has been resolved:

ubifs: Fix memory leak in do_rename

If renaming a file in an encrypted directory, function
fscrypt_setup_filename allocates memory for a file name. This name is
never used, and before returning to the caller the memory for it is not
freed.

When running kmemleak on it we see that it is registered as a leak. The
report below is triggered by a simple program 'rename' that renames a
file in an encrypted directory:

  unreferenced object 0xffff888101502840 (size 32):
    comm "rename", pid 9404, jiffies 4302582475 (age 435.735s)
    backtrace:
      __kmem_cache_alloc_node
      __kmalloc
      fscrypt_setup_filename
      do_rename
      ubifs_rename
      vfs_rename
      do_renameat2

To fix this we can remove the call to fscrypt_setup_filename as it's not
needed.

The Linux kernel CVE team has assigned CVE-2023-53396 to this issue.


Affected and fixed versions
===========================

	Issue introduced in 5.15.33 with commit c67bc98d1f0853bb196e9c48eab38b6f2ddab795 and fixed in 5.15.112 with commit 43b2f7d690697182beed6f71aa57b7249d3cfc9c
	Issue introduced in 5.18 with commit 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 and fixed in 6.1.28 with commit 9f565752b328fe53c9e42b7d4e4d89a1da63d738
	Issue introduced in 5.18 with commit 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 and fixed in 6.2.15 with commit 7e264f67b7d6580eff5c2696961039fd05c69258
	Issue introduced in 5.18 with commit 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 and fixed in 6.3.2 with commit 517ddc0259d7a7231486bdafde8035c478bc4088
	Issue introduced in 5.18 with commit 278d9a243635f26c05ad95dcf9c5a593b9e04dc6 and fixed in 6.4 with commit 3a36d20e012903f45714df2731261fdefac900cb
	Issue introduced in 5.16.19 with commit 17495eb2f7f08113b50aba298c2c1a045824c4f7
	Issue introduced in 5.17.2 with commit 868de33a39e0e1e91ed3ce4a23a65f30144d2443

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-53396
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/dir.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/43b2f7d690697182beed6f71aa57b7249d3cfc9c
	https://git.kernel.org/stable/c/9f565752b328fe53c9e42b7d4e4d89a1da63d738
	https://git.kernel.org/stable/c/7e264f67b7d6580eff5c2696961039fd05c69258
	https://git.kernel.org/stable/c/517ddc0259d7a7231486bdafde8035c478bc4088
	https://git.kernel.org/stable/c/3a36d20e012903f45714df2731261fdefac900cb