From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@kernel.org>
Subject: CVE-2026-64075: fprobe: Fix unregister_fprobe() to wait for RCU grace period
Date: Sun, 19 Jul 2026 17:38:57 +0200 [thread overview]
Message-ID: <2026071914-CVE-2026-64075-4eb1@gregkh> (raw)
From: Greg Kroah-Hartman <gregkh@kernel.org>
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
reply other threads:[~2026-07-19 15:42 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2026071914-CVE-2026-64075-4eb1@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=gregkh@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox