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 939B433EAF9 for ; Sat, 22 Aug 2026 15:34:12 +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=1787412853; cv=none; b=WN8mZJGoe+tnkINiTUrQMDi1PmjRIrUlJtbNyhJDcM1n/Yl/WGEeaGSSPG6Wed34Ct9lMal1ZrhBk1ZLfPse7F18mJ6k8ngE51w3qDEc45ORo9ko9+ZSNSFZ2LThfCKDc5TSTbde5IWP0YJTs/Q2jPoiatHZwQjwK8MluSVdHrM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1787412853; c=relaxed/simple; bh=E8HkL2kN2ObmhJXSUhTSke8aCMPpExq9DCf/IP4lwbg=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=daqIgV/BGLoAOiZeTDzgaJFjVJTjTM9gyPbBklUpBnZ99CS8tyw96fuc/2PNb34d0D+FUVYnFyKkRcheC+g560gSf1Q9B9cTo51zCiEg+CjEeecGTEotaglW8mtwXiHZvFziZYI9Z6rU44sYibnvF0fOa7zit1ig1sBoLnU+LDA= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=S+y6AHYu; 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="S+y6AHYu" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 605701F000E9; Sat, 22 Aug 2026 15:34:11 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1787412851; bh=iB08C5OYKZKNdDQgsja2wymmlQyNsfHka3+B3URvbV0=; h=From:To:Cc:Subject:Date:Reply-To; b=S+y6AHYuWNm0H0b+yLt2vGiJ2rjFM0QL4LQ/jVuOc2HUpRM5byf+w6p4mPjf7EnW2 P6NtIA0UOuQpfmHxn3BBfYKPwISdNolfp1EPbFcMhv2nCoEPzA702A69It7d3jqT0F oSy8cl0gMnItRcQzGdwLEJ+Pb+xD5Q+u9nPdzUAs= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-74605: eventfs: Use children field for rcu head and add memory barriers Date: Sat, 22 Aug 2026 17:31:29 +0200 Message-ID: <2026082216-CVE-2026-74605-94d2@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=2807; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=P3fKoJL6jdKQ7QGMprp3Kd6k9uYu68KNccuCySPTeAI=; b=owGbwMvMwCRo6H6F97bub03G02pJDFmdB45050T1rwo5emf9AfMII7kLiV8NpLP6Pod0/jTxc bo0ax5PRywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAExE5wjDgpboKaKZZ4u+fAjJ 4T6jpVStutXwH8M8m6I97teFvVrnPRHTd7t1a/9x9W0xAA== 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: eventfs: Use children field for rcu head and add memory barriers When an eventfs inode is freed, it sets ei->is_freed and then uses its ei->list to add it to the srcu link list as the list field is a union with the rcu list head. As the ei->list is used to iterate over an SRCU protected list without taking the eventfs_mutex, there's nothing stopping the iteration over that list to see the ei->rcu instead of the ei->list and it will read a corrupt target. To fix this, change the union of the rcu list head with the children list. On freeing the eventfs inode, set the is_free and execute a smp_wmb() before adding the eventfs inode to the SRCU list. On iteration of the ei->children list, at the start, execute a smp_rmb() and then read the is_freed of the ei to see if the children list is still valid. If is_freed is set, then the ei_child read is not valid and the loop should exit immediately. The Linux kernel CVE team has assigned CVE-2026-74605 to this issue. Affected and fixed versions =========================== Issue introduced in 6.8 with commit 704f960dbee2f1634f4b4e16f208cb16eaf41c1e and fixed in 7.1.9 with commit 004f7232e49730448f91665e76bdd7dff8e0c638 Issue introduced in 6.8 with commit 704f960dbee2f1634f4b4e16f208cb16eaf41c1e and fixed in 7.2 with commit f0ece16ffca7384787b692431961ce202907acf5 Issue introduced in 6.6.18 with commit f3f41f444b321ec393edbc251e024fd62658ce55 Issue introduced in 6.7.6 with commit 305c4e4d80aca2c2d9cf2ebdea56e2eca6d3a6aa 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-74605 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/tracefs/event_inode.c fs/tracefs/internal.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/004f7232e49730448f91665e76bdd7dff8e0c638 https://git.kernel.org/stable/c/f0ece16ffca7384787b692431961ce202907acf5