CVE-2025-71309 Details
Description
In the Linux kernel, the following vulnerability has been resolved: fs/ntfs3: fix deadlock in ni_read_folio_cmpr Syzbot reported a task hung in ni_readpage_cmpr (now ni_read_folio_cmpr). This is caused by a lock inversion deadlock involving the inode mutex (ni_lock) and page locks. Scenario: 1. Task A enters ntfs_read_folio() for page X. It acquires ni_lock. 2. Task A calls ni_read_folio_cmpr(), which attempts to lock all pages in the compressed frame (including page Y). 3. Concurrently, Task B (e.g., via readahead) has locked page Y and calls ntfs_read_folio(). 4. Task B waits for ni_lock (held by A). 5. Task A waits for page Y lock (held by B). -> DEADLOCK. The fix is to restructure locking: do not take ni_lock in ntfs_read_folio(). Instead, acquire ni_lock inside ni_read_folio_cmpr() ONLY AFTER all required page locks for the frame have been successfully acquired. This restores the correct lock ordering (Page Lock -> ni_lock) consistent with VFS. [[email protected]: ni_readpage_cmpr was renamed to ni_read_folio_cmpr]
A deadlock vulnerability has been identified in the Linux kernel's NTFS3 file system implementation, specifically in the handling of compressed frames. This deadlock arises from a lock inversion issue between the inode mutex and page locks. The problem occurs when one task holds the inode lock and attempts to lock pages in a compressed frame, while another task has already locked one of those pages and is waiting for the inode lock, creating a circular wait condition.
The vulnerability has been addressed by changing the locking mechanism. The inode lock should not be acquired in the 'ntfs_read_folio' function. Instead, it should be obtained in 'ni_read_folio_cmpr' only after all necessary page locks have been secured, restoring the correct lock order consistent with the Virtual File System (VFS) requirements.
Metrics
CVSS 4.0 Severity and Vector Strings:
No CVSS 4.0 data is available for this CVE.
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
No SSVC data is available for this CVE.
References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://git.kernel.org/stable/c/cfe246b318106e1691bd6c9466c739e8559d25c2 | kernel.org | Patch |
| https://git.kernel.org/stable/c/e37a75bb866c29da954b51d0dd7670406246d9ee | kernel.org | Patch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-667 | Improper Locking | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| linux linux kernel | >= 6.19, < 6.19.4 |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 14, 2026 | CVE Translated | [email protected] |
| Jun 25, 2026 | Initial Analysis | [email protected] |
| Jun 17, 2026 | CVE Modified | kernel.org |
| May 27, 2026 | New CVE Received | kernel.org |