<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 30 Sep 2026 23:37:45 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-23309 — tracing: Add NULL pointer check to trigger_data_free()</title>
      <link>https://db.gcve.eu/vuln/cve-2026-23309</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Add NULL pointer check to trigger_data_free()&lt;/p&gt;
&lt;p&gt;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-&amp;gt;cmd_ops-&amp;gt;set_filter.&lt;/p&gt;
&lt;p&gt;Fix the problem by adding a NULL pointer check to trigger_data_free().&lt;/p&gt;
&lt;p&gt;The problem was found by an experimental code review agent based on
gemini-3.1-pro while reviewing backports into v6.18.y.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;tracing: Add NULL pointer check to trigger_data_free()&lt;/p&gt;
&lt;p&gt;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-&amp;gt;cmd_ops-&amp;gt;set_filter.&lt;/p&gt;
&lt;p&gt;Fix the problem by adding a NULL pointer check to trigger_data_free().&lt;/p&gt;
&lt;p&gt;The problem was found by an experimental code review agent based on
gemini-3.1-pro while reviewing backports into v6.18.y.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-23309</guid>
    </item>
  </channel>
</rss>
