Description
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.
Metrics
CVSS 3.1 5.5/10
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:HWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= c10f0efe57728508d796ae4ba7abe4c14ec3d8ef, < 13dcd9269e225e4c4ceabdaeebe2ce4661b54c6e; >= 7e6556e9329bc484e9dcdab6e346d959267c0636, < 59c15b9cc453b74beb9f04c6c398717e73612dc3; >= 9b0513905e0598b9f8cfccab8e47497aed5d935d, < 42b380f97d65e76e7b310facd525f730272daf57; >= 335dfe4bc6368e70e8c15419375cf609c4f85558, < 2ce8ece5a78da67834db7728edc801889a64f643; >= e42efbe9754da78eafe11f6bd3ca9c8a094a752a, < 477469223b2b840f436ce204333de87cb17e5d93; >= 0550069cc25f513ce1f109c88f7c1f01d63297db, < 457965c13f0837a289c9164b842d0860133f6274 |
| Linux | Linux | >= 6.1.165, < 6.1.167; >= 6.6.128, < 6.6.130; >= 6.12.75, < 6.12.77; >= 6.18.14, < 6.18.17; >= 6.19.4, < 6.19.7 |
References
- https://git.kernel.org/stable/c/13dcd9269e225e4c4ceabdaeebe2ce4661b54c6ePatch
- https://git.kernel.org/stable/c/2ce8ece5a78da67834db7728edc801889a64f643Patch
- https://git.kernel.org/stable/c/42b380f97d65e76e7b310facd525f730272daf57Patch
- https://git.kernel.org/stable/c/457965c13f0837a289c9164b842d0860133f6274Patch
- https://git.kernel.org/stable/c/477469223b2b840f436ce204333de87cb17e5d93Patch
- https://git.kernel.org/stable/c/59c15b9cc453b74beb9f04c6c398717e73612dc3Patch
Timeline
- Published
- Mar 25, 2026
- Last modified
- Jun 17, 2026
- NVD status
- Analyzed