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 B04173A759C for ; Sun, 19 Jul 2026 15:42:20 +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=1784475742; cv=none; b=HGMUzShDoYhnM0Sk8qMJXrPI2CByuNPzSjZoCe3dSB+QxD+UcWxLn0bz4+rKRN1mPjbWSUzu6xS9dJUn39vo8q1mzDMMOpxR+PVuqiFoy0HU8TNJdLfsmaq3YLTR5fwKhtBzcUbMBx4A3mfVSxHT7or/nFMLgaYU7gZoQky+nDg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784475742; c=relaxed/simple; bh=xwAXMfrBEpB4inxdjvnR6Ns6sokSDsxPNPe5wPEosRk=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=O9RSy9JzuohvpQyLisP1bM9mQ36YNsaqMsyHeGD0Q7saGdnHeRUbtxu1NuEF+x/z7QYhrgwai4YK9/0VcxwgxYFql7ptfx4drZmUpxm2AoF2yo0u0kH/roqm4SIo0PZdP9hkSoPZqmg5N+lUg5qgPlI9WZCiVlM4Jf9ws3c2rTI= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=AmnlhvP/; 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="AmnlhvP/" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 05C791F000E9; Sun, 19 Jul 2026 15:42:19 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784475740; bh=rc3vaXLJK4R+z3XGTeNydUxcIU0h8nNIStFQUGXSw2k=; h=From:To:Cc:Subject:Date:Reply-To; b=AmnlhvP/Lrkf166PTxonk0tMBk83PNA/i2tuQeoKwMUPatYQkznvrQIEcMGCs8gWx GqqOkEWtQU++L5I4lb1cxJ5eC5YfEC/JDVrp63HlCxU3HMx3M2vWkAgdJpEhyL92Nk gDPNwM1m1rKG+wc1HV7ibrvxfHusKOXMe2amQE6s= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64067: netfs: Fix missing barriers when accessing stream->subrequests locklessly Date: Sun, 19 Jul 2026 17:38:49 +0200 Message-ID: <2026071912-CVE-2026-64067-9bf7@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=2968; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=n7nG8zp6+UDOUBCNycVRCAXNzth3jDTHVZRqFhur4VM=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkx71OqJSZrBkjfqVp94PMB1U3X5izb67sj9UTxWbMDm 5WPPP8m0RHLwiDIxCArpsjyZRvP0f0VhxS9DG1Pw8xhZQIZwsDFKQATeRvLMIu5nbvGUTrjzd6z HYKOV/inWAVc3cswh+ObwMrGuR1ajTkfebPku+69y/riAgA= 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: netfs: Fix missing barriers when accessing stream->subrequests locklessly The list of subrequests attached to stream->subrequests is accessed without locks by netfs_collect_read_results() and netfs_collect_write_results(), and then they access subreq->flags without taking a barrier after getting the subreq pointer from the list. Relatedly, the functions that build the list don't use any sort of write barrier when constructing the list to make sure that the NETFS_SREQ_IN_PROGRESS flag is perceived to be set first if no lock is taken. Fix this by: (1) Add a new list_add_tail_release() function that uses a release barrier to set the pointer to the new member of the list. (2) Add a new list_first_entry_or_null_acquire() function that uses an acquire barrier to read the pointer to the first member in a list (or return NULL). (3) Use list_add_tail_release() when adding a subreq to ->subrequests. (4) Use list_first_entry_or_null_acquire() when initially accessing the front of the list (when an item is removed, the pointer to the new front iterm is obtained under the same lock). The Linux kernel CVE team has assigned CVE-2026-64067 to this issue. Affected and fixed versions =========================== Issue introduced in 6.10 with commit 288ace2f57c9d06dd2e42bd80d03747d879a4068 and fixed in 7.0.11 with commit 293a4532c36f38458e38b8879b174ab797718b9d Issue introduced in 6.10 with commit 288ace2f57c9d06dd2e42bd80d03747d879a4068 and fixed in 7.1 with commit b5782e2d462c028096f922abca46318cec890670 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-64067 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/netfs/buffered_read.c fs/netfs/misc.c fs/netfs/read_collect.c fs/netfs/write_collect.c fs/netfs/write_issue.c include/linux/list.h 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/293a4532c36f38458e38b8879b174ab797718b9d https://git.kernel.org/stable/c/b5782e2d462c028096f922abca46318cec890670