linux-cve-announce - CVE-2023-53163: fs/ntfs3: don't hold ni_lock when calling truncate

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: <2025091553-CVE-2023-53163-860f@gregkh>
Date: Mon, 15 Sep 2025 16:02:17 +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-53163: fs/ntfs3: don't hold ni_lock when calling truncate_setsize()

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

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

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

fs/ntfs3: don't hold ni_lock when calling truncate_setsize()

syzbot is reporting hung task at do_user_addr_fault() [1], for there is
a silent deadlock between PG_locked bit and ni_lock lock.

Since filemap_update_page() calls filemap_read_folio() after calling
folio_trylock() which will set PG_locked bit, ntfs_truncate() must not
call truncate_setsize() which will wait for PG_locked bit to be cleared
when holding ni_lock lock.

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


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

	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 5.15.87 with commit 8414983c2e649364d8af29080a0869266b31abb6
	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 6.0.19 with commit 6bb6b1c6b0c31e36736b87a39dd1cbbd9d5ec22f
	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 6.1.5 with commit 73fee7e1e5ea11b51c51c46e0577a197ca3602cf
	Issue introduced in 5.15 with commit 4342306f0f0d5ff4315a204d315c1b51b914fca5 and fixed in 6.2 with commit 0226635c304cfd5c9db9b78c259cb713819b057e

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-53163
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/file.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/8414983c2e649364d8af29080a0869266b31abb6
	https://git.kernel.org/stable/c/6bb6b1c6b0c31e36736b87a39dd1cbbd9d5ec22f
	https://git.kernel.org/stable/c/73fee7e1e5ea11b51c51c46e0577a197ca3602cf
	https://git.kernel.org/stable/c/0226635c304cfd5c9db9b78c259cb713819b057e