fprobe: Fix unregister_fprobe() to wait for RCU grace period
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.34, 7.0.11
- CVEs
- CVE-2026-64075
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 6 Nov 2026, 00:39 UTC · Revision 1
Source evidence
fprobe: Fix unregister_fprobe() to wait for RCU grace period
core-osv · Original sourcePublished 19 Jul 2026, 15:39 UTC
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.
osv:CVE-2026-64075
Kernel
Fixed versions: 6.18.34, 7.0.11
Complete source record
{
"id": "db6fbf3da12e6c4eb6f6c1d7c5b03e29e925994b65fed8684f6d5be061ed1fd0",
"url": "https://osv.dev/vulnerability/CVE-2026-64075",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "fprobe: Fix unregister_fprobe() to wait for RCU grace period",
"summary": "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.",
"evidence": "osv:CVE-2026-64075",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.34",
"evidence": "/affected/1/ranges"
},
{
"value": "7.0.11",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-64075",
"aliases": [
"CVE-2026-64075"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "4346ba1604093305a287e08eb465a9c15ba05b80"
},
{
"fixed": "56b4cfcf1518245493c60fd39c56978f508f1816"
},
{
"fixed": "a4f6a9005ed6cfd360ef2520430927f05f92ffb0"
},
{
"fixed": "657b594b2084b39a4bc6d8493aa2140cb00cea49"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64075.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.14.0"
},
{
"fixed": "6.18.34"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.0.11"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-64075.json"
}
}
],
"modified": "2026-10-28T02:30:45.802279316Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/56b4cfcf1518245493c60fd39c56978f508f1816",
"https://git.kernel.org/stable/c/657b594b2084b39a4bc6d8493aa2140cb00cea49",
"https://git.kernel.org/stable/c/a4f6a9005ed6cfd360ef2520430927f05f92ffb0",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64075.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-64075",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64075.json"
}
},
"related_cves": [
{
"value": "CVE-2026-64075",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 513558,
"published_at": "2026-07-19T15:39:49.679+00:00"
}