Vulnerability · Published Aug 15, 2026 · Assigned by Linux

CVE-2026-72203ntfs: skip extent mft records in writeback to prevent deadlock

High 7.5

In plain English

A high-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 50% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)7.5High
Exploit odds (30 days)0.6%top 49.6% of all CVEs
Exploited in the wildNo reportsnot in CISA KEV
Attack toolingNoneno public tooling known

Official 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.

Affected packages & fixed versions

EcosystemPackageFixed inAdvisory
Debian:12linuxno fix listedDEBIAN-CVE-2026-72203
Debian:14linux7.1.5-1DEBIAN-CVE-2026-72203
Ubuntu:22.04:LTSlinuxno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinuxno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinuxno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-allwinner-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-awsno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-aws-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-aws-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-aws-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-aws-6.2no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-aws-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-aws-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-aws-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-azureno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azure-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-6.11no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azure-6.2no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azure-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azure-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-azure-fdeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azure-fde-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-fde-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-fde-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azure-fde-6.2no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-azure-fde-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-fde-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-nvidiano fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-azure-nvidia-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-gcpno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-gcp-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-gcp-6.11no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-gcp-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-gcp-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-gcp-6.2no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-gcp-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-gcp-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-gcp-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-gkeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-gkeopno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-hwe-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-hwe-6.11no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-hwe-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-hwe-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-hwe-6.2no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-hwe-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-hwe-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-hwe-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-ibmno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-ibm-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-intel-iot-realtimeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-intel-iotgno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-kvmno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-lowlatencyno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-lowlatency-hwe-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-lowlatency-hwe-6.11no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.2no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-lowlatency-hwe-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-nvidiano fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-nvidia-6.11no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-nvidia-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-nvidia-6.2no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-nvidia-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-nvidia-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-nvidia-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-nvidia-bosno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-nvidia-lowlatencyno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-nvidia-tegrano fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-nvidia-tegra-igxno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-oem-5.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-oem-6.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-oem-6.1no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-oem-6.11no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-oem-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-oem-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-oem-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-oem-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-oem-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-oracleno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-oracle-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-oracle-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-oracle-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-oracle-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-oracle-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-raspino fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-raspi-realtimeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-realtimeno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72203
Ubuntu:26.04:LTSlinux-riscvno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-riscv-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-riscv-6.14no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-riscv-6.17no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-riscv-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-riscv-6.8no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-riscv-7.0no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-starfive-5.19no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-starfive-6.2no fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-starfive-6.5no fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-vmwareno fix listedUBUNTU-CVE-2026-72203
Ubuntu:24.04:LTSlinux-xilinxno fix listedUBUNTU-CVE-2026-72203
Ubuntu:22.04:LTSlinux-xilinx-zynqmpno fix listedUBUNTU-CVE-2026-72203

Affected products (as reported)

VendorProductVersions
Linux Linux 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before b06b4fc2138ded8ee0b3dc602991ff6dbb10dd0a1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 6626fb859f4c4772f2f59751d23937716e03f98f1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 – before 7ffa8f3d30236e0ab897c30bdb01224ff1fe1c891e9ea7e04472d4e5e12e58c881eaacfb3e49b669 – before f831ab09d521898bf1dd99bf5adfd630ea1428e31e9ea7e04472d4e5e12e58c881eaacfb3e49b669 – before 76bc14c7097ff678b2b5dbfd4fa33b46897d87ce
Linux Linux 2.6.127.1

References