{"api_version":"1","generated_at":"2026-07-22T13:17:42+00:00","cve":"CVE-2026-64075","urls":{"html":"https://cve.report/CVE-2026-64075","api":"https://cve.report/api/cve/CVE-2026-64075.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-64075","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-64075"},"summary":{"title":"fprobe: Fix unregister_fprobe() to wait for RCU grace period","description":"In the Linux kernel, the following vulnerability has been resolved:\n\nfprobe: Fix unregister_fprobe() to wait for RCU grace period\n\nCommit 4346ba1604093 (\"fprobe: Rewrite fprobe on function-graph tracer\")\nchanged fprobe to register struct fprobe to an rcu-hlist, but it forgot\nto wait for RCU GP. Thus there can be use-after-free if the fprobe is\nreleased right after unregistering. This can be happened on fprobe\nevent and sample module code.\n\nTo fix this issue, add synchronize_rcu() in unregister_fprobe().\n\nNote that BPF is OK because fprobe is used as a part of\nbpf_kprobe_multi_link. This unregisters its fprobe in\nbpf_kprobe_multi_link_release() and it is deallocated via\nbpf_kprobe_multi_link_dealloc(), which is invoked from\nbpf_link_defer_dealloc_rcu_gp() RCU callback.\n\nFor BPF, this also introduced unregister_fprobe_async() which does\nNOT wait for RCU grace priod.","state":"PUBLISHED","assigner":"Linux","published_at":"2026-07-19 16:17:48","updated_at":"2026-07-19 16:17:48"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/56b4cfcf1518245493c60fd39c56978f508f1816","name":"https://git.kernel.org/stable/c/56b4cfcf1518245493c60fd39c56978f508f1816","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/a4f6a9005ed6cfd360ef2520430927f05f92ffb0","name":"https://git.kernel.org/stable/c/a4f6a9005ed6cfd360ef2520430927f05f92ffb0","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/657b594b2084b39a4bc6d8493aa2140cb00cea49","name":"https://git.kernel.org/stable/c/657b594b2084b39a4bc6d8493aa2140cb00cea49","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-64075","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-64075","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4346ba1604093305a287e08eb465a9c15ba05b80 56b4cfcf1518245493c60fd39c56978f508f1816 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4346ba1604093305a287e08eb465a9c15ba05b80 a4f6a9005ed6cfd360ef2520430927f05f92ffb0 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4346ba1604093305a287e08eb465a9c15ba05b80 657b594b2084b39a4bc6d8493aa2140cb00cea49 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.14","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.14 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.34 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.11 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"64075","cve":"CVE-2026-64075","epss":"0.001660000","percentile":"0.061660000","score_date":"2026-07-20","updated_at":"2026-07-21 00:13:14"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["include/linux/fprobe.h","kernel/trace/bpf_trace.c","kernel/trace/fprobe.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"56b4cfcf1518245493c60fd39c56978f508f1816","status":"affected","version":"4346ba1604093305a287e08eb465a9c15ba05b80","versionType":"git"},{"lessThan":"a4f6a9005ed6cfd360ef2520430927f05f92ffb0","status":"affected","version":"4346ba1604093305a287e08eb465a9c15ba05b80","versionType":"git"},{"lessThan":"657b594b2084b39a4bc6d8493aa2140cb00cea49","status":"affected","version":"4346ba1604093305a287e08eb465a9c15ba05b80","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["include/linux/fprobe.h","kernel/trace/bpf_trace.c","kernel/trace/fprobe.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.14"},{"lessThan":"6.14","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.34","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.11","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.34","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.11","versionStartIncluding":"6.14","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1","versionStartIncluding":"6.14","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\nfprobe: Fix unregister_fprobe() to wait for RCU grace period\n\nCommit 4346ba1604093 (\"fprobe: Rewrite fprobe on function-graph tracer\")\nchanged fprobe to register struct fprobe to an rcu-hlist, but it forgot\nto wait for RCU GP. Thus there can be use-after-free if the fprobe is\nreleased right after unregistering. This can be happened on fprobe\nevent and sample module code.\n\nTo fix this issue, add synchronize_rcu() in unregister_fprobe().\n\nNote that BPF is OK because fprobe is used as a part of\nbpf_kprobe_multi_link. This unregisters its fprobe in\nbpf_kprobe_multi_link_release() and it is deallocated via\nbpf_kprobe_multi_link_dealloc(), which is invoked from\nbpf_link_defer_dealloc_rcu_gp() RCU callback.\n\nFor BPF, this also introduced unregister_fprobe_async() which does\nNOT wait for RCU grace priod."}],"providerMetadata":{"dateUpdated":"2026-07-19T15:39:49.679Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/56b4cfcf1518245493c60fd39c56978f508f1816"},{"url":"https://git.kernel.org/stable/c/a4f6a9005ed6cfd360ef2520430927f05f92ffb0"},{"url":"https://git.kernel.org/stable/c/657b594b2084b39a4bc6d8493aa2140cb00cea49"}],"title":"fprobe: Fix unregister_fprobe() to wait for RCU grace period","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-64075","datePublished":"2026-07-19T15:39:49.679Z","dateReserved":"2026-07-19T07:54:57.031Z","dateUpdated":"2026-07-19T15:39:49.679Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-07-19 16:17:48","lastModifiedDate":"2026-07-19 16:17:48","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"64075","Ordinal":"1","Title":"fprobe: Fix unregister_fprobe() to wait for RCU grace period","CVE":"CVE-2026-64075","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"64075","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\nfprobe: Fix unregister_fprobe() to wait for RCU grace period\n\nCommit 4346ba1604093 (\"fprobe: Rewrite fprobe on function-graph tracer\")\nchanged fprobe to register struct fprobe to an rcu-hlist, but it forgot\nto wait for RCU GP. Thus there can be use-after-free if the fprobe is\nreleased right after unregistering. This can be happened on fprobe\nevent and sample module code.\n\nTo fix this issue, add synchronize_rcu() in unregister_fprobe().\n\nNote that BPF is OK because fprobe is used as a part of\nbpf_kprobe_multi_link. This unregisters its fprobe in\nbpf_kprobe_multi_link_release() and it is deallocated via\nbpf_kprobe_multi_link_dealloc(), which is invoked from\nbpf_link_defer_dealloc_rcu_gp() RCU callback.\n\nFor BPF, this also introduced unregister_fprobe_async() which does\nNOT wait for RCU grace priod.","Type":"Description","Title":"fprobe: Fix unregister_fprobe() to wait for RCU grace period"}]}}}