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 6A0E4488206 for ; Fri, 25 Sep 2026 10:28:02 +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=1790332083; cv=none; b=IF67NQv9MHz5HXxKq3LDEbLJHhWoR8b/1A47RQfsVdN3CRlp26M4drY8nUSkoRbxOzcR0bFCTfYiIP7SJ3iNmo/jCq63BHPvJClkacZRqlfnL4F9lAiNN8bEkanmMCdQqUjKQuhmmFriCDjWcjmw7IZnjcyCnSqALnSjxJawZaA= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1790332083; c=relaxed/simple; bh=ufYxZyoqz+K35a4ZGgLKTUODffGxCbH3gn4AFMr99H0=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=T4ZWXSPMfYv987zlCkLeZnTSFHn1I7WET0vgjDthoU3OGcHnyqSfpourTt2vLnMSfvzSfvcjUNXZE79G28e7xXPwrKNXTTHb4DfW7DWTnvxzXQhiJ2GLPFW0+3LViorpO7/vRpnZpBh/TxLArBE7AsxuVIC28ALNlopjN5oozS8= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=mgdVFoCx; 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="mgdVFoCx" Received: by smtp.kernel.org (Postfix) with ESMTPSA id AB6001F000FF; Fri, 25 Sep 2026 10:28:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1790332082; bh=2CRyUTikA7gYARSlhm7fMxJqSjcJjxku7BOkbWi9EAQ=; h=From:To:Cc:Subject:Date:Reply-To; b=mgdVFoCxfJTTEVlPXN6ItTHvtJ+t2I/u8BZHE1S3bLJAJFLbN37S2UsjGHByum35z RhMnze4l3Dw0bkNlTnLq1dhWDQOJTXSv3V/X9e1p+tlF34Q0wQftNmd9Ol9OtNv9u8 hFRzo6l73+crAPd1TSlrDLWQ3dnfQAUiMZb254VU= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-97619: io_uring/rw: end write accounting from ->ki_complete Date: Fri, 25 Sep 2026 12:23:19 +0200 Message-ID: <2026092503-CVE-2026-97619-e0b9@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=3726; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=oogI4dOgaEqt+2uokk8P+DNUTBq9RUmJ7t/17ExqTtI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFnbvL2nuF+a0C9Zfkcxyz4qXtHx8FWnB2Enr1s8flDpI p109m5LRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEzkQwjDgo2nMt/ayJ852e7d YZenrfoubuZkboZ51lXWOjJvn9xtdec7ZHKyzfT05RMHAQ== 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: io_uring/rw: end write accounting from ->ki_complete Commit b000145e9907 moved both the fsnotify calls and the write accounting out of the kiocb completion handler and into the io_req_rw_complete() task_work. However, only the fsnotify part actually needed to move as it may sleep. Ending the write accounting is just a percpu_up_read() on the superblock writers sem. Deferring it is a problem, because it makes dropping SB_FREEZE_WRITE protection depend on the ring owner getting to running task_work. But the task may be blocked in freeze_super(), causing it to never get to that: task io-wq worker -------------------------------------------------------------- io_write() io_kiocb_start_write() (takes sb_writers, hidden from lockdep by __sb_writers_release) write_iter() -> -EIOCBQUEUED ioctl(FS_IOC_SHUTDOWN) bdev_freeze() freeze_super() percpu_down_write() <- waits for the reader above io_write() kiocb_start_write() percpu_down_read() <- queued behind the writer io_complete_rw() queues io_req_rw_complete() <- never runs, task is in D state End the write from io_complete_rw() instead, and leave only the fsnotify calls in task_work. The Linux kernel CVE team has assigned CVE-2026-97619 to this issue. Affected and fixed versions =========================== Issue introduced in 6.1 with commit b000145e9907809406d8164c3b2b8861d95aecd1 and fixed in 6.18.53 with commit cc580cee4dfa2ec9099c30ecbd4d804cbb996432 Issue introduced in 6.1 with commit b000145e9907809406d8164c3b2b8861d95aecd1 and fixed in 7.2.7 with commit 055d43a1233edbd80e558889258105ce63051bcd Issue introduced in 6.1 with commit b000145e9907809406d8164c3b2b8861d95aecd1 and fixed in 7.3-rc3 with commit 796aa0547557e63338657ed1c487906f9fac4c73 Issue introduced in 5.10.165 with commit ea2e6286e3e89a115ae554e20ba9aec2b2e1ddff Issue introduced in 5.15.90 with commit 89a410dbd0f159ddd308f19d6eb682fc753e4771 Issue introduced in 6.0.3 with commit 2a853c206e553dd9c0a55c22858fd6a446d93e15 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-97619 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: io_uring/rw.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/cc580cee4dfa2ec9099c30ecbd4d804cbb996432 https://git.kernel.org/stable/c/055d43a1233edbd80e558889258105ce63051bcd https://git.kernel.org/stable/c/796aa0547557e63338657ed1c487906f9fac4c73