tracing: Add NULL pointer check to trigger_data_free()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 0550069cc25f513ce1f109c88f7c1f01d63297db · < 457965c13f0837a289c9164b842d0860133f6274| No fix yet |
| Linux Linux |
| No fix yet |
In the Linux kernel, the following vulnerability has been resolved:
tracing: Add NULL pointer check to trigger_data_free()
If trigger_data_alloc() fails and returns NULL, event_hist_trigger_parse() jumps to the out_free error path. While kfree() safely handles a NULL pointer, trigger_data_free() does not. This causes a NULL pointer dereference in trigger_data_free() when evaluating data->cmd_ops->set_filter.
Fix the problem by adding a NULL pointer check to trigger_data_free().
The problem was found by an experimental code review agent based on gemini-3.1-pro while reviewing backports into v6.18.y.
From the CVE record · Linux
In the Linux kernel's tracing code, a failed trigger data allocation can lead to a NULL pointer dereference during error handling. The input does not establish whether an attacker can trigger this condition or specify network access, authentication, or user-interaction requirements.
Engineers running the Linux kernel should check their installations; affected versions are not specified.