UBUNTU-CVE-2026-72192

In the Linux kernel, the following vulnerability has been resolved: ntfs3: bound tomove in indxinsertintoroot before hdrinserthead indxinsertintoroot promotes a full resident $INDEXROOT into $INDEXALLOCATION and copies all non-last resident root entries into a newly allocated INDEXBUFFER via...

EUVD-2026-59376

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: call ntfsbadinode when failing to rename It is safe to call ntfsbadinode on live inodes since: commit 519b078998ce "fs/ntfs3: Exclude call makebadinode for live nodes." The WARNON was added when it wasn't safe by: commi...

EUVD-2026-59377

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: add bounds check to rungethighestvcn rungethighestvcn parses a packed NTFS mapping-pairs buffer without any length bound, relying solely on a 0x00 terminator to stop. A crafted $LogFile UpdateMappingPairs record whose...

CVE-2026-72478 fs/ntfs3: add bounds check to run_get_highest_vcn()

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: add bounds check to rungethighestvcn rungethighestvcn parses a packed NTFS mapping-pairs buffer without any length bound, relying solely on a 0x00 terminator to stop. A crafted $LogFile UpdateMappingPairs record whose...

CVE-2026-72477 fs/ntfs3: call _ntfs_bad_inode() when failing to rename

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: call ntfsbadinode when failing to rename It is safe to call ntfsbadinode on live inodes since: commit 519b078998ce "fs/ntfs3: Exclude call makebadinode for live nodes." The WARNON was added when it wasn't safe by: commi...

CVE-2026-72478

The CVE describes a bound-checking fix in Linux kernel ntfs3 (fs/ntfs3) for run_get_highest_vcn(), which previously parsed a packed NTFS mapping-pairs buffer without length bounds and could read past the slab allocation, triggering a KASAN slab-out-of-bounds read on mount. The patch adds a run_bu...

CVE-2026-72477 fs/ntfs3: call _ntfs_bad_inode() when failing to rename

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: call ntfsbadinode when failing to rename It is safe to call ntfsbadinode on live inodes since: commit 519b078998ce "fs/ntfs3: Exclude call makebadinode for live nodes." The WARNON was added when it wasn't safe by: commi...

CVE-2026-72477

The CVE-2026-72477 entry concerns the Linux kernel (fs/ntfs3) where a failure to rename could trigger an inconsistent inode state. The root issue was a WARN_ON path; it has been replaced with a call to _ntfs_bad_inode(), preventing further operations on the affected inode. This change appears to ...

CVE-2026-72478 fs/ntfs3: add bounds check to run_get_highest_vcn()

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: add bounds check to rungethighestvcn rungethighestvcn parses a packed NTFS mapping-pairs buffer without any length bound, relying solely on a 0x00 terminator to stop. A crafted $LogFile UpdateMappingPairs record whose...

CVE-2026-72471 fs/ntfs3: prevent potential lcn remains uninitialized

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: prevent potential lcn remains uninitialized The target VCN being sought was not found within runs0, causing runlookup to return false. This causes runlookupentry to return false, which in turn results in a len value of ...

EUVD-2026-59370

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: prevent potential lcn remains uninitialized The target VCN being sought was not found within runs0, causing runlookup to return false. This causes runlookupentry to return false, which in turn results in a len value of ...

CVE-2026-72471

CVE-2026-72471: In the Linux kernel (ntfs3) vulnerability, a path where target VCN isn’t found could lead run_lookup() to false, causing a chain that results in attr_data_get_block() receiving a NULL and finally exit without initializing lcn. The fix prevents this by moving the clen check in ni_s...

CVE-2026-72471 fs/ntfs3: prevent potential lcn remains uninitialized

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: prevent potential lcn remains uninitialized The target VCN being sought was not found within runs0, causing runlookup to return false. This causes runlookupentry to return false, which in turn results in a len value of ...

CVE-2026-72470 fs/ntfs3: resize log->one_page_buf when adopting on-disk page size

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: resize log-onepagebuf when adopting on-disk page size logreplay allocates log-onepagebuf using the page size that was chosen from the host PAGESIZE: log-onepagebuf = kmalloclog-pagesize, GFPNOFS; Later, when a restart...

CVE-2026-72470 fs/ntfs3: resize log->one_page_buf when adopting on-disk page size

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: resize log-onepagebuf when adopting on-disk page size logreplay allocates log-onepagebuf using the page size that was chosen from the host PAGESIZE: log-onepagebuf = kmalloclog-pagesize, GFPNOFS; Later, when a restart...

EUVD-2026-59369

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: resize log-onepagebuf when adopting on-disk page size logreplay allocates log-onepagebuf using the page size that was chosen from the host PAGESIZE: log-onepagebuf = kmalloclog-pagesize, GFPNOFS; Later, when a restart...

CVE-2026-72470

The CVE-2026-72470 vulnerability affects the Linux kernel fs/ntfs3 sub-system. log_replay() initially allocates log->one_page_buf using the host’s PAGE_SIZE, but when an on-disk restart area specifies a larger page size, log->page_size is updated, while one_page_buf may remain undersized. S...

CVE-2026-72197 fs/ntfs3: bound DeleteIndexEntryAllocation memmove length

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound DeleteIndexEntryAllocation memmove length In doaction's DeleteIndexEntryAllocation case, e-size comes from an on-disk INDEXBUFFER entry. When e-size makes e + e-size point past hdr + hdr-used, PtrOffsete1,...

CVE-2026-72197

The CVE-2026-72197 issue affects the Linux kernel, specifically the fs/ntfs3 path for DeleteIndexEntryAllocation. The root cause is that e->size can cause an overlong memmove when e + e->size points past hdr + hdr->used, leading to a dangerous memmove length. A corresponding guard alread...

CVE-2026-72197 fs/ntfs3: bound DeleteIndexEntryAllocation memmove length

In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: bound DeleteIndexEntryAllocation memmove length In doaction's DeleteIndexEntryAllocation case, e-size comes from an on-disk INDEXBUFFER entry. When e-size makes e + e-size point past hdr + hdr-used, PtrOffsete1,...