From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id DBEFA3CF66B for ; Wed, 27 May 2026 12:20:07 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779884409; cv=none; b=H+Jmhgbn2lPtuEGp2iNgoDrpWI9YxFjEUclS/vna8E+ZCLkhiXhHigrHVqS4/pcRzQZ+gLftrH/gayyoxN1v9rpY+RW2/V2rbCAU294Fzal/iTdetKGy2tlnJ/L8Pd31etMO0PV/yMLeu8izzrIAOtGwXhpF0EaitvYF4PVoF/8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1779884409; c=relaxed/simple; bh=wvqYSGEOt7FNSksXUS3FLKVBsG7LzYk5AhQsFGXobqc=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=rEMVc2/MIl7L/WriTlNVUhLtaaPEf1G0e1JP5pQwhFTim+ETN0IgMtsR35eJcx0eC0dhZEwdZniRRrlozvZWaPEsDutl9UM2FPKANfL0L4xyYrfwevtS6xwoKN/JyHGckNFEA8cixKIuGTvYQwMQS+RZ1u6KdCs1VMda1tv9Ql8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=Tbz4jIPY; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b="Tbz4jIPY" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2DA881F000E9; Wed, 27 May 2026 12:20:06 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1779884407; bh=Zp4TuGLgvcfhBzL2DWauYbl9qOah6MVwqw3JYc559bY=; h=From:To:Cc:Subject:Date:Reply-To; b=Tbz4jIPY+F3CUZuvAfIM+JjIf5/RRx0crDNC02X7YUh9jSassgZNszQohvYCe+99y HBx7ElcYEVv/yyoPBWEc2eymP+CwrfCGbX6yFhV7U/pAveryI6gLgZuKkOq7MAmKdW ROaFVARE/0sWmNOSQCZIFaKqhrmg1SGA4sex8E7w= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2025-71309: fs/ntfs3: fix deadlock in ni_read_folio_cmpr Date: Wed, 27 May 2026 14:18:08 +0200 Message-ID: <2026052707-CVE-2025-71309-9e3c@gregkh> X-Mailer: git-send-email 2.54.0 Reply-To: , Precedence: bulk X-Mailing-List: linux-cve-announce@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 X-Developer-Signature: v=1; a=openpgp-sha256; l=2740; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=LsNol3wjdmvAWFT2699dMgWMab4L7fgUGmq7tDMAVMI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFliD/5zsv/5Idl21yrn45znDDtnRZ1zyvHNzl8beqrLb oqr+ZunHbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRlEKGeTbhvt/qVyl5hBeU pio/qGJfpLL/MMNc2dvvj4pft7V63a/1eM+2Jvm9b8v3AAA= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman 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. [almaz.alexandrovich@paragon-software.com: ni_readpage_cmpr was renamed to ni_read_folio_cmpr] The Linux kernel CVE team has assigned CVE-2025-71309 to this issue. Affected and fixed versions =========================== Issue introduced in 6.19 with commit f35590ee26f5722bfe12cdff14396c4c057a8f74 and fixed in 6.19.4 with commit cfe246b318106e1691bd6c9466c739e8559d25c2 Issue introduced in 6.19 with commit f35590ee26f5722bfe12cdff14396c4c057a8f74 and fixed in 7.0 with commit e37a75bb866c29da954b51d0dd7670406246d9ee Please see https://www.kernel.org for a full list of currently supported kernel versions by the kernel community. Unaffected versions might change over time as fixes are backported to older supported kernel versions. The official CVE entry at https://cve.org/CVERecord/?id=CVE-2025-71309 will be updated if fixes are backported, please check that for the most up to date information about this issue. Affected files ============== The file(s) affected by this issue are: fs/ntfs3/frecord.c fs/ntfs3/inode.c Mitigation ========== The Linux kernel CVE team recommends that you update to the latest stable kernel version for this, and many other bugfixes. Individual changes are never tested alone, but rather are part of a larger kernel release. Cherry-picking individual commits is not recommended or supported by the Linux kernel community at all. If however, updating to the latest release is impossible, the individual changes to resolve this issue can be found at these commits: https://git.kernel.org/stable/c/cfe246b318106e1691bd6c9466c739e8559d25c2 https://git.kernel.org/stable/c/e37a75bb866c29da954b51d0dd7670406246d9ee