tracing: Don't dereference trace_event_file in deferred trigger free
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
7.2.77.3In the Linux kernel, the following vulnerability has been resolved:
tracing: Don't dereference trace_event_file in deferred trigger free
The enable_event trigger defers trace_event_put_ref() to the trigger free kthread, but the trace_event_file can already be freed when the instance is removed.
Keep the trace_event_call directly in enable_trigger_data so the deferred free does not access the freed trace_event_file.
From the CVE record · Linux
The Linux kernel's tracing code can access a freed trace_event_file during deferred enable_event trigger cleanup if the tracing instance has already been removed. The input does not specify an attacker capability, access requirements, or whether user interaction is needed.
Engineers running the Linux kernel should check their versions against the vendor advisory; affected versions are not specified.