CVE-2026-43127

ntfs3: fix circular locking dependency in run_unpack_ex

MEDIUM
5.5
CVSS Score
Published: May 6, 2026 at 11:27 AM UTC
Updated: October 21, 2026 at 01:18 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.1%

Description

In the Linux kernel, the following vulnerability has been resolved: ntfs3: fix circular locking dependency in run_unpack_ex Syzbot reported a circular locking dependency between wnd->rw_lock (sbi->used.bitmap) and ni->file.run_lock. The deadlock scenario: 1. ntfs_extend_mft() takes ni->file.run_lock then wnd->rw_lock. 2. run_unpack_ex() takes wnd->rw_lock then tries to acquire ni->file.run_lock inside ntfs_refresh_zone(). This creates an AB-BA deadlock. Fix this by using down_read_trylock() instead of down_read() when acquiring run_lock in run_unpack_ex(). If the lock is contended, skip ntfs_refresh_zone() - the MFT zone will be refreshed on the next MFT operation. This breaks the circular dependency since we never block waiting for run_lock while holding wnd->rw_lock.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.19 ≤ v < 6.19.66.6.66 ≤ v < 6.18.1657f7979aefdcef66326bda47e07ee0d8be64bf215fc982fe7eca9d0cf7b25832450ebd4f7c8e1c366.12.56.136.6.66db7fc56646cafe39599a4c21f1398e2bdfd5c185
Vendor states this is fixed in 08ce2fee1b869ecbfbd94e0eb2630e52203a2e03 (fixed)
Vendor states this is fixed in b014372b62237521444ee51384549bdf48b79015 (fixed)
Vendor states this is fixed in b8d22d9d8260b0f4f4d8e2898c98037c9982ea66 (fixed)
Vendor states this is fixed in 6.12.114 (unaffected)
Vendor states this is fixed in 6.13 (unaffected)
Vendor states this is fixed in 6.18.16 (unaffected)
Vendor states this is fixed in 6.19.6 (unaffected)
Vendor states this is fixed in 6.6.160 (unaffected)
Affected range stops below 6.7, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 7.0 (unaffected)

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-667

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card