<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://db.gcve.eu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T23:37:45.138001+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@gcve.eu</email>
  </author>
  <link href="https://db.gcve.eu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://db.gcve.eu/vuln/cve-2026-23309</id>
    <title>CVE-2026-23309 — tracing: Add NULL pointer check to trigger_data_free()</title>
    <updated>2026-09-30T23:37:45.150205+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>tracing: Add NULL pointer check to trigger_data_free()</p>
<p>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-&gt;cmd_ops-&gt;set_filter.</p>
<p>Fix the problem by adding a NULL pointer check to trigger_data_free().</p>
<p>The problem was found by an experimental code review agent based on
gemini-3.1-pro while reviewing backports into v6.18.y.</p></div>
    </content>
    <link href="https://db.gcve.eu/vuln/cve-2026-23309"/>
  </entry>
</feed>
