Bug 2562675 (CVE-2026-99102) - CVE-2026-99102 kernel: ntfs: take invalidate_lock in ntfs_setattr_size()
Summary: CVE-2026-99102 kernel: ntfs: take invalidate_lock in ntfs_setattr_size()
Keywords:
Status: NEW
Alias: CVE-2026-99102
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-10-28 10:47 UTC by OSIDB Bzimport
Modified: 2026-10-28 13:43 UTC (History)
17 users (show)

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


Attachments (Terms of Use)

Description OSIDB Bzimport 2026-10-28 10:47:56 UTC
In the Linux kernel, the following vulnerability has been resolved:

ntfs: take invalidate_lock in ntfs_setattr_size()

ntfs_setattr_size() updates i_size and resizes the on-disk attribute
without holding mapping->invalidate_lock.  Page faults take the lock
shared, so a fault racing the resize can resolve a VCN against the
transient runlist state of ntfs_non_resident_attr_expand() and fail
with a spurious SIGBUS, and can interleave with the size-change
epilogue (truncate_pagecache(), i_size_write(),
pagecache_isize_extended()).

Take invalidate_lock exclusively around the whole resize after
inode_dio_wait(), matching the fallocate path and other filesystems
such as xfs, which wraps truncate in its mmaplock (= invalidate_lock).


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