CVE-2026-97443

perf/ftrace: Fix WARNING in __unregister_ftrace_function

N/A
Published: September 24, 2026 at 04:03 PM UTC
Updated: September 25, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

In the Linux kernel, the following vulnerability has been resolved: perf/ftrace: Fix WARNING in __unregister_ftrace_function perf_ftrace_function_unregister() unconditionally calls unregister_ftrace_function() without checking whether the ftrace_ops was ever successfully registered. This triggers a WARN_ON in __unregister_ftrace_function() when the ops doesn't have FTRACE_OPS_FL_ENABLED set. This can happen during perf_event_alloc() error cleanup when perf_trace_destroy() is called via __free_event() on an event whose ftrace_ops registration failed or was already torn down by perf_try_init_event()'s err_destroy path. The call path is: perf_event_alloc() error cleanup -> __free_event() -> event->destroy() [tp_perf_event_destroy] -> perf_trace_destroy() -> perf_trace_event_close() -> TRACE_REG_PERF_CLOSE -> perf_ftrace_function_unregister() -> unregister_ftrace_function() -> __unregister_ftrace_function() -> WARN_ON(!(ops->flags & FTRACE_OPS_FL_ENABLED)) Fix this by checking FTRACE_OPS_FL_ENABLED before attempting to unregister. If the ops is not enabled, just free the filter and return success.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v ≥ 6.13.12v ≥ 6.14.36.12.24 ≤ v < 6.12.1116.13.12 ≤ v < 6.146.14.3 ≤ v < 6.156.15 ≤ v < 6.18.536.15 ≤ v < 7.21209b0b29fd472e7dbd2b06544b019dd9f9b7e51315a50c6b1c6ce191f19f3372935d8e2ed9b53a66.12.246.13.126.14.36.157ef5aa081f989ecfecc1df02068a80aebbd3ec31c70ca298036c58a88686ff388d3d367e9d21acf0
Vendor states this is fixed in 7f845820afaad339341c2ae42bc7fdec175df9ea (fixed)
Vendor states this is fixed in 9581123304b23049437324038698af9fb56ee663 (fixed)
Vendor states this is fixed in df097713b56ffac5eed32a9be2e7d27ac48d9087 (fixed)
Vendor states this is fixed in 6.12.111 (unaffected)
Affected range stops below 6.14, so it looks safe — our inference, not a vendor statement
Vendor states this is fixed in 6.15 (unaffected)
Vendor states this is fixed in 6.18.53 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card