Live › vulnerability › CVE-2026-99102
Go to dashboardThe Linux kernel's NTFS driver resizes files without holding the invalidate_lock, so a page fault during the resize can fail with a spurious SIGBUS. The sources describe a race condition that crashes or fails memory-mapped access rather than a clearly described code-execution path.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-28 11:32 UTC. All times on this page are UTC.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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).
This page as .md · .json · in your agent: get_signal("CVE-2026-99102")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.