CVE-2026-97443: perf/ftrace: Fix WARNING in __unregister_ftrace_function

Published Sep 24, 2026
·
Updated

In the Linux kernel, the following vulnerability has been resolved:

perf/ftrace: Fix WARNING in unregisterftracefunction

perfftracefunctionunregister() unconditionally calls unregisterftracefunction() without checking whether the ftraceops was ever successfully registered. This triggers a WARNON in unregisterftracefunction() when the ops doesn't have FTRACEOPSFLENABLED set.

This can happen during perfeventalloc() error cleanup when perftracedestroy() is called via freeevent() on an event whose ftraceops registration failed or was already torn down by perftryinitevent()'s errdestroy path.

The call path is: perfeventalloc() error cleanup -> freeevent() -> event->destroy() [tpperfeventdestroy] -> perftracedestroy() -> perftraceeventclose() -> TRACEREGPERFCLOSE -> perfftracefunctionunregister() -> unregisterftracefunction() -> unregisterftracefunction() -> WARNON(!(ops->flags & FTRACEOPSFLENABLED))

Fix this by checking FTRACEOPSFLENABLED before attempting to unregister. If the ops is not enabled, just free the filter and return success.

Affected Software

1 affected component
Linux Linux kernel

Event History

Sep 24, 2026
CVE Published
via MITRE·04:03 PM
Data Sourced
via MITRE·04:03 PM
Description
Data Sourced
via NVD·05:17 PM
Description

Frequently Asked Questions

1

Under what conditions can this warning occur?

It can occur during perf_event_alloc() error cleanup when ftrace-ops registration failed, or when the operations were already torn down through perf_try_init_event() error handling. The cleanup path then attempts to unregister operations that were never successfully enabled.

2

Does exploitation require an attacker to have access to perf event creation or tracing functionality?

The provided information identifies the triggering path as perf event allocation and trace-event cleanup, but does not state attacker prerequisites, privilege requirements, or a remote attack vector.

3

What is the mitigation if the fix cannot be applied immediately?

No operational workaround is provided. The described fix is to avoid unregistering ftrace operations unless the FTRACE_OPS_FL_ENABLED flag is set, and otherwise free the filter and return success.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203