linux-cve-announce - CVE-2023-53294: fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs

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: <2025091627-CVE-2023-53294-e5cc@gregkh>
Date: Tue, 16 Sep 2025 10:11:44 +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-53294: fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup()

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

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

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

fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup()

Syzbot reported a null-ptr-deref bug:

ntfs3: loop0: Different NTFS' sector size (1024) and media sector size
(512)
ntfs3: loop0: Mark volume as dirty due to NTFS errors
general protection fault, probably for non-canonical address
0xdffffc0000000001: 0000 [#1] PREEMPT SMP KASAN
KASAN: null-ptr-deref in range [0x0000000000000008-0x000000000000000f]
RIP: 0010:d_flags_for_inode fs/dcache.c:1980 [inline]
RIP: 0010:__d_add+0x5ce/0x800 fs/dcache.c:2796
Call Trace:
 <TASK>
 d_splice_alias+0x122/0x3b0 fs/dcache.c:3191
 lookup_open fs/namei.c:3391 [inline]
 open_last_lookups fs/namei.c:3481 [inline]
 path_openat+0x10e6/0x2df0 fs/namei.c:3688
 do_filp_open+0x264/0x4f0 fs/namei.c:3718
 do_sys_openat2+0x124/0x4e0 fs/open.c:1310
 do_sys_open fs/open.c:1326 [inline]
 __do_sys_open fs/open.c:1334 [inline]
 __se_sys_open fs/open.c:1330 [inline]
 __x64_sys_open+0x221/0x270 fs/open.c:1330
 do_syscall_x64 arch/x86/entry/common.c:50 [inline]
 do_syscall_64+0x3d/0xb0 arch/x86/entry/common.c:80
 entry_SYSCALL_64_after_hwframe+0x63/0xcd

If the MFT record of ntfs inode is not a base record, inode->i_op can be
NULL. And a null-ptr-deref may happen:

ntfs_lookup()
    dir_search_u() # inode->i_op is set to NULL
    d_splice_alias()
        __d_add()
            d_flags_for_inode() # inode->i_op->get_link null-ptr-deref

Fix this by adding a Check on inode->i_op before calling the
d_splice_alias() function.

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


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

	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 5.15.112 with commit f8d9e062a695a3665c4635c4f216a75912687598
	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 6.1.29 with commit d69d5e2a81df94534bdb468bcdd26060fcb7191a
	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 6.2.16 with commit 2ba22cbc6a1cf4b58195adbee0b80262e53992d3
	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 6.3.3 with commit e78240bc4b94fc42854d65e657bb998100cc8e1b
	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 6.4 with commit 254e69f284d7270e0abdc023ee53b71401c3ba0c

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-53294
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/namei.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/f8d9e062a695a3665c4635c4f216a75912687598
	https://git.kernel.org/stable/c/d69d5e2a81df94534bdb468bcdd26060fcb7191a
	https://git.kernel.org/stable/c/2ba22cbc6a1cf4b58195adbee0b80262e53992d3
	https://git.kernel.org/stable/c/e78240bc4b94fc42854d65e657bb998100cc8e1b
	https://git.kernel.org/stable/c/254e69f284d7270e0abdc023ee53b71401c3ba0c