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 673933A7590 for ; Sun, 19 Jul 2026 15:42:45 +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=1784475766; cv=none; b=HEmGD21xr7J2Mo8Xbo+hbPFr1MYYI6JnfY/TvSZQS3afsiDpAEVVSJaLDJH9UZX5e2XnW/7sAL8OoteHtn+4JbDiRrU2+GP6t/kKfykE/Vq+JhuOiyUEeO+nO80qSyp5ZMxg3Vk/Go34ptAyr7Yyh73yVV/NKxkJK2E6ylyWRfY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784475766; c=relaxed/simple; bh=LnBzfF8iWrZqKtkWkd/DuMcGgm4uXLgQFkk6KN/0x44=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=cAXQvK5GtVFZUrSJjY2bN0x42x9CE55Nr9FQOan4ZGn9MmuOVC0g+fM8hVhqGjKyQj7Wj68sauCezBRjbxkGYHyChBQH633e6XDBfPmHbTxQDR65N6E/jqr17U87psHwS6DTrQ5TGlfrJfz8mhk9ysX+/s5yQCaKJ2/nHoh5m84= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=linuxfoundation.org header.i=@linuxfoundation.org header.b=oFK1n5PI; 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="oFK1n5PI" Received: by smtp.kernel.org (Postfix) with ESMTPSA id CAF761F000E9; Sun, 19 Jul 2026 15:42:44 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linuxfoundation.org; s=korg; t=1784475765; bh=s8Lsk+BRtxrp6BrJzYNUvyibdMt2rviDa4aBnPImjEM=; h=From:To:Cc:Subject:Date:Reply-To; b=oFK1n5PI/3gG4JhhdUkLmMqb52MaATHzMqY98nTJyVsfgNr9q6gvb2GB2CoOZA3v8 48/nWcFr75pB1gDnCi/c6fjpVOr5nn2dSm+ipzrm9ZgssnvadXjID2fAP+tJgxcY8L TkER6bVKBI7TE4crWK7hGRCTeT/Y95hQ8XVjPUUY= From: Greg Kroah-Hartman To: linux-cve-announce@vger.kernel.org Cc: Greg Kroah-Hartman Subject: CVE-2026-64075: fprobe: Fix unregister_fprobe() to wait for RCU grace period Date: Sun, 19 Jul 2026 17:38:57 +0200 Message-ID: <2026071914-CVE-2026-64075-4eb1@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=2805; i=gregkh@linuxfoundation.org; h=from:subject:message-id; bh=hFtyoGURcKBGMfZSAnyj9xf/MlB3dET4RqHiAxMpxH0=; b=owGbwMvMwCRo6H6F97bub03G02pJDFkx79M+Vef+NfxwdPkEg7ikkw9Xt1zJ42k+WqIvX/Miu T1PSfFARywLgyATg6yYIsuXbTxH91ccUvQytD0NM4eVCWQIAxenAEwk6z7D/KyZcrffVm2Oc7Nf FNZ+P/DwLt8wToYF8xz+rWQ+sI0tWCDFP835bbPf+6KrAA== 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: fprobe: Fix unregister_fprobe() to wait for RCU grace period Commit 4346ba1604093 ("fprobe: Rewrite fprobe on function-graph tracer") changed fprobe to register struct fprobe to an rcu-hlist, but it forgot to wait for RCU GP. Thus there can be use-after-free if the fprobe is released right after unregistering. This can be happened on fprobe event and sample module code. To fix this issue, add synchronize_rcu() in unregister_fprobe(). Note that BPF is OK because fprobe is used as a part of bpf_kprobe_multi_link. This unregisters its fprobe in bpf_kprobe_multi_link_release() and it is deallocated via bpf_kprobe_multi_link_dealloc(), which is invoked from bpf_link_defer_dealloc_rcu_gp() RCU callback. For BPF, this also introduced unregister_fprobe_async() which does NOT wait for RCU grace priod. The Linux kernel CVE team has assigned CVE-2026-64075 to this issue. Affected and fixed versions =========================== Issue introduced in 6.14 with commit 4346ba1604093305a287e08eb465a9c15ba05b80 and fixed in 6.18.34 with commit 56b4cfcf1518245493c60fd39c56978f508f1816 Issue introduced in 6.14 with commit 4346ba1604093305a287e08eb465a9c15ba05b80 and fixed in 7.0.11 with commit a4f6a9005ed6cfd360ef2520430927f05f92ffb0 Issue introduced in 6.14 with commit 4346ba1604093305a287e08eb465a9c15ba05b80 and fixed in 7.1 with commit 657b594b2084b39a4bc6d8493aa2140cb00cea49 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-64075 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: include/linux/fprobe.h kernel/trace/bpf_trace.c kernel/trace/fprobe.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/56b4cfcf1518245493c60fd39c56978f508f1816 https://git.kernel.org/stable/c/a4f6a9005ed6cfd360ef2520430927f05f92ffb0 https://git.kernel.org/stable/c/657b594b2084b39a4bc6d8493aa2140cb00cea49