CVE-2026-72203
Received Received - Intake

Deadlock in Linux Kernel NTFS Writeback

Vulnerability report for CVE-2026-72203, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-15

Last updated on: 2026-08-19

Assigner: kernel.org

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs: skip extent mft records in writeback to prevent deadlock This patch fixes the ABBA deadlock between extent_lock and extent mrec_lock triggered by xfstests generic/113, that occurs since the commit 6994acf33bae ("ntfs: use base mft_no when looking up base inode for extent record"). Path A (inode writeback): VFS writeback -> ntfs_write_inode() -> __ntfs_write_inode() -> mutex_lock(&ni->extent_lock) -> mutex_lock(&tni->mrec_lock) Path B (MFT folio writeback): VFS writeback of $MFT dirty folios -> ntfs_mft_writepages() -> ntfs_write_mft_block() -> ntfs_may_write_mft_record() -> holds one extent mrec_lock from a previous iteration -> tries to acquire another base inode extent_lock By removing all extent_lock and extent mrec_lock acquisition from the MFT folio writeback path, the ABBA lock ordering is eliminated: Path A: __ntfs_write_inode(): extent_lock -> mrec_lock Path B (removed): ntfs_write_mft_block(): mrec_lock -> extent_lock Path B is always redundant for extent records because: 1. mark_mft_record_dirty(ext_ni) does NOT dirty the MFT folio. It only sets NInoDirty(ext_ni) and marks the base VFS inode dirty via __mark_inode_dirty(I_DIRTY_DATASYNC), which triggers Path A. Therefore, normal extent modifications never create a situation where the MFT folio is dirty and Path B is not scheduled. 2. The MFT folio only gets dirtied via ntfs_mft_mark_dirty() inside ntfs_mft_record_alloc(). But all identified callers in attrib.c (ntfs_attr_add, ntfs_attr_record_move_away, ntfs_attr_make_non_resident, ntfs_attr_record_resize) follow through with mark_mft_record_dirty(), which triggers Path A to write the complete record. 3. ntfs_evict_big_inode() calls ntfs_commit_inode() before freeing extent inodes, ensuring all dirty extents are flushed via Path A before the base inode leaves the icache.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-15
Last Modified
2026-08-19
Generated
2026-09-04
AI Q&A
2026-08-15
EPSS Evaluated
2026-09-03
NVD
EUVD

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-UNKNOWN

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability in the Linux kernel involves an ABBA deadlock in the NTFS filesystem. It occurs when two threads attempt to acquire locks in opposite orders during writeback operations. One path locks extent_lock then mrec_lock, while another path locks mrec_lock then extent_lock, creating a circular dependency that can freeze the system.

Detection Guidance

This vulnerability is specific to the Linux kernel's NTFS implementation and does not have a direct network detection method. To check if your system is affected, verify the kernel version and NTFS driver code for the presence of the described deadlock issue. Use commands like 'uname -a' to check the kernel version and inspect the NTFS driver source code for the relevant patches.

Impact Analysis

This vulnerability can cause system freezes or crashes during filesystem operations on NTFS volumes. Users may experience unresponsive systems, data corruption risks, or forced reboots when the deadlock occurs during disk write operations.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA. It is a Linux kernel deadlock issue in the NTFS filesystem that could lead to system instability or crashes but does not involve data exposure or privacy violations.

Mitigation Strategies

Apply the latest kernel updates that include the fix for this vulnerability. If you are using a vulnerable kernel version, upgrade to a patched version or apply the specific patch that resolves the ABBA deadlock in the NTFS writeback path. Monitor kernel security advisories for updates related to CVE-2026-72203.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-72203. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart