linux-cve-announce - CVE-2023-54272: fs/ntfs3: Fix a possible null-pointer dereference in ni

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: <2025123001-CVE-2023-54272-cb3f@gregkh>
Date: Tue, 30 Dec 2025 13:20:38 +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-54272: fs/ntfs3: Fix a possible null-pointer dereference in ni_clear()

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

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

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

fs/ntfs3: Fix a possible null-pointer dereference in ni_clear()

In a previous commit c1006bd13146, ni->mi.mrec in ni_write_inode()
could be NULL, and thus a NULL check is added for this variable.

However, in the same call stack, ni->mi.mrec can be also dereferenced
in ni_clear():

ntfs_evict_inode(inode)
  ni_write_inode(inode, ...)
    ni = ntfs_i(inode);
    is_rec_inuse(ni->mi.mrec) -> Add a NULL check by previous commit
  ni_clear(ntfs_i(inode))
    is_rec_inuse(ni->mi.mrec) -> No check

Thus, a possible null-pointer dereference may exist in ni_clear().
To fix it, a NULL check is added in this function.

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


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

	Fixed in 5.15.113 with commit 20f9bfc664d6a478f9a5bbc0c380f80f7a1a06c6
	Fixed in 6.1.81 with commit 39c6312009574ca73865354133ca222e7753a71b
	Fixed in 6.3.4 with commit e7675f85a92233136c630000a0b7cf97826705da
	Fixed in 6.4 with commit ec275bf9693d19cc0fdce8436f4c425ced86f6e7

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-54272
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/ntfs3/frecord.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/20f9bfc664d6a478f9a5bbc0c380f80f7a1a06c6
	https://git.kernel.org/stable/c/39c6312009574ca73865354133ca222e7753a71b
	https://git.kernel.org/stable/c/e7675f85a92233136c630000a0b7cf97826705da
	https://git.kernel.org/stable/c/ec275bf9693d19cc0fdce8436f4c425ced86f6e7