CVE-2023-53294: fs/ntfs3: Fix null-ptr-deref on inode->i_op in ntfs_lookup()
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.
Security readout for executives and security teams
Plain-English summary
This is a Linux kernel availability issue in the NTFS3 filesystem driver. A local user who can cause the system to process a malformed NTFS filesystem condition may trigger a kernel null pointer dereference and crash the system. The available sources do not show data theft, privilege escalation, or active exploitation.
Executive priority
Handle as a moderate-priority Linux kernel maintenance item. Patch affected systems through normal kernel update channels, with higher priority for systems that mount NTFS media or inspect disk images. The main business risk is service disruption, not confirmed compromise.
Technical view
In fs/ntfs3 ntfs_lookup(), a non-base NTFS MFT record can leave inode->i_op as NULL. The code then calls d_splice_alias(), which can reach d_flags_for_inode() and dereference inode->i_op->get_link. The kernel fix adds an inode->i_op check before d_splice_alias().
Likely exposure
Exposure is most relevant to Linux systems using affected kernels with NTFS3 support and workflows that mount or inspect NTFS filesystems. Systems that never load or use NTFS3 are less likely exposed. The source bundle lists affected Linux kernel versions and stable kernel fixes but does not identify specific distributions.
Exploitation context
The CVSS vector is local, low complexity, low privilege, no user interaction, with high availability impact only. KEV is false, and the provided sources do not report active exploitation. Evidence points to denial of service through a kernel crash, originally found by syzbot.
Researcher notes
The record describes CWE-476 and a KASAN null pointer dereference in the NTFS3 lookup path. Affected version data is kernel-centric and distribution mapping is not provided. Do not assume exploit availability or distribution package status without vendor advisories.
Mitigation direction
Apply vendor or distribution kernel updates that include the NTFS3 fix.
Confirm whether your kernel includes the referenced stable commits or equivalent backport.
Reduce use of NTFS3 on systems that do not need NTFS support.
Avoid processing untrusted NTFS media or images until patched.
Track Linux kernel and distribution advisories for CVE-2023-53294.
Validation and detection
Inventory Linux systems and identify kernels with NTFS3 support enabled.
Check kernel package changelogs for CVE-2023-53294 or referenced stable commits.
Review whether servers or workstations mount NTFS removable media or disk images.
Look for recent kernel crashes or logs mentioning ntfs3 errors.
Prioritize validation on multi-user systems and systems handling user-supplied storage media.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-476: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-476 · source CWE mapping
NULL Pointer Dereference
NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.