Bug 2395341 (CVE-2023-53163) - CVE-2023-53163 kernel: fs/ntfs3: don't hold ni_lock when calling truncate_setsize()
Summary: CVE-2023-53163 kernel: fs/ntfs3: don't hold ni_lock when calling truncate_set...
Keywords:
Status: NEW
Alias: CVE-2023-53163
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-09-15 15:08 UTC by OSIDB Bzimport
Modified: 2026-01-06 09:44 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-09-15 15:08:32 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.