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 52BF04F054D for ; Fri, 4 Sep 2026 15:58:23 +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=1788537504; cv=none; b=qvzI6dpBBYewxwZ3cfk+jQqm0knC7oyKHqrv2DU4NdwTkKcKJ7xT/7Go6Pj7LbgoOzxcKGExku/IYNZIGL+aTZBg8rwy3DG+dIcpnSh2FpHRYDnE14QQbzCfDOQoZwRgOrDmKLo3qvk78CKY7jK55iKLPgHej8GARvzSBlUKQqo= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1788537504; c=relaxed/simple; bh=lGnow6YXAT007D7zN8B8KM1JVzgSEDN7dDiOg1Zk7a4=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type; b=JovDYBmZiUE6MxyEWPtu60bgDzcLfGJbk5VMtKMWggT71G2/Mf2nusVLmNeY3rbVOOikqvVjKVR8agL123ESDY90ISqlKZC4nGd3h07QAZIzmffOQwx+seQreIajsjslzT8p9eKiL4bVY8sJCO934nOvTtr+JP8FMO8TaZkkyqI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=FDbNIZoY; 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="FDbNIZoY" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 399351F00ACF; Fri, 4 Sep 2026 15:58:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1788537503; bh=VOCLnAhYkkMQ4qtoFibGqiO16qETWIkwcCSMOGkMOOc=; h=From:To:Cc:Subject:Date:Reply-To; b=FDbNIZoY+dnNJyU6oPgwc5nFUTPVrK6WztW46sQR3HAJqzPf9XkARBPlVPEhzCdUC 9JvupZNA7JeW4Ej2oEPXm1iaqHFDA8OcE0GiUZFxRZX7VI+MPf7Z9cW7RTzvy1zTGG piLps8hwN6p4G28sCIU3KNy9SpKQMn59dSMri9MI= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-80855: fuse: fix invalidate lock leak on open O_TRUNC DAX failure Date: Fri, 4 Sep 2026 17:53:22 +0200 Message-ID: <2026090401-CVE-2026-80855-6028@gregkh> X-Mailer: git-send-email 2.55.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=4446; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=YKO7czIZKu4PdFNO7UALaSuLzA8ykTx+ORxCZa8RqO4=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmzXsY+c3/vu/SQZq1xb4dEuuma20pLntzb/ZltR2p8t v7Pv6Y6HbEsDIJMDLJiiixftvEc3V9xSNHL0PY0zBxWJpAhDFycAjCRa08ZFuxjXCh13KP05r/S 6RNqrjaZ6d8/tY9hfonjzI3LZWZ7Vc9k3bp629GOhpXyvwE= X-Developer-Key: i=gregkh@linuxfoundation.org; a=openpgp; fpr=F4B60CC5BF78C2214A313DCB3147D40DDB2DFB29 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit From: Greg Kroah-Hartman Description =========== In the Linux kernel, the following vulnerability has been resolved: fuse: fix invalidate lock leak on open O_TRUNC DAX failure fuse_open() takes filemap_invalidate_lock() for a DAX truncate (dax_truncate = true) and releases it before the out_inode_unlock label. But when fuse_dax_break_layouts() fails, the goto out_inode_unlock skips the unlock and leaks the rwsem, so any later fault or truncate on the file stalls on the stale lock. fuse_dax_break_layouts() can fail with -ERESTARTSYS when a signal interrupts the wait for busy DAX pages to drain: open("file", O_RDWR | O_TRUNC) └─ fuse_open() ├─ filemap_invalidate_lock() # dax_truncate └─ fuse_dax_break_layouts() └─ dax_break_layout() └─ wait_page_idle() # TASK_INTERRUPTIBLE └─ fuse_wait_dax_page() # unlock, schedule, re-lock └─ signal → -ERESTARTSYS goto out_inode_unlock # <- lock leaked Fix this by moving filemap_invalidate_unlock() below the label so that all error paths release the lock, and rename the label to out_unlock as it now covers more than just the inode lock. The Linux kernel CVE team has assigned CVE-2026-80855 to this issue. Affected and fixed versions =========================== Issue introduced in 5.15.109 with commit d58366aab86854217b81679d1a9dcd54a2edfc2a and fixed in 5.15.220 with commit 1b04d80a27d317064cce2307472f5bef9975bc50 Issue introduced in 6.0 with commit 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and fixed in 6.1.187 with commit a61524da59a2f5ac9c8de23ff98b30da769ab144 Issue introduced in 6.0 with commit 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and fixed in 6.6.156 with commit dcf30a56624c2a0cfab1bada5b1ca8cc0c02f010 Issue introduced in 6.0 with commit 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and fixed in 6.12.108 with commit 7288c279ddbd654a06c82118c1a3f5570c1807f0 Issue introduced in 6.0 with commit 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and fixed in 6.18.49 with commit 776e85fda752f9a15e0f82dec42ecacd12a9bd94 Issue introduced in 6.0 with commit 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and fixed in 7.1.13 with commit 1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da Issue introduced in 6.0 with commit 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and fixed in 7.2.3 with commit e981474d7bf1457da12404e169ea147d2c8ecea7 Issue introduced in 6.0 with commit 2fdbb8dd01556e1501132b5ad3826e8f71e24a8b and fixed in 7.3-rc1 with commit a927f1867e61b78f39f9da0bbba3c98c2ca151fe Issue introduced in 5.10.179 with commit 81775ab858b4236c52c5da7e25cec6e49dd91b46 Issue introduced in 5.18.18 with commit b57e150ac2eac791d5d187923b73dc2dafaf67fa Issue introduced in 5.19.2 with commit 1fdbbe246daf348adaa0739463384b16ceba1fc0 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-2026-80855 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/fuse/file.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/1b04d80a27d317064cce2307472f5bef9975bc50 https://git.kernel.org/stable/c/a61524da59a2f5ac9c8de23ff98b30da769ab144 https://git.kernel.org/stable/c/dcf30a56624c2a0cfab1bada5b1ca8cc0c02f010 https://git.kernel.org/stable/c/7288c279ddbd654a06c82118c1a3f5570c1807f0 https://git.kernel.org/stable/c/776e85fda752f9a15e0f82dec42ecacd12a9bd94 https://git.kernel.org/stable/c/1d3e701cda2f41d48aa721b3ebefbe0fbf8d74da https://git.kernel.org/stable/c/e981474d7bf1457da12404e169ea147d2c8ecea7 https://git.kernel.org/stable/c/a927f1867e61b78f39f9da0bbba3c98c2ca151fe