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.
References 6
https://git.kernel.org/stable/c/13dcd9269e225e4c4ceabdaeebe2ce4661b54c6e
416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/2ce8ece5a78da67834db7728edc801889a64f643
416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/42b380f97d65e76e7b310facd525f730272daf57
416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/457965c13f0837a289c9164b842d0860133f6274
416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/477469223b2b840f436ce204333de87cb17e5d93
416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/59c15b9cc453b74beb9f04c6c398717e73612dc3
416baaa9-dc9f-4396-8d5f-8c081fb06d67