<?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://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-01T20:00:31.982468+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" 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://vulnerability.circl.lu/vuln/cve-2026-31481</id>
    <title>CVE-2026-31481 — tracing: Drain deferred trigger frees if kthread creation fails</title>
    <updated>2026-10-01T20:00:32.009486+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: Drain deferred trigger frees if kthread creation fails</p>
<p>Boot-time trigger registration can fail before the trigger-data cleanup
kthread exists. Deferring those frees until late init is fine, but the
post-boot fallback must still drain the deferred list if kthread
creation never succeeds.</p>
<p>Otherwise, boot-deferred nodes can accumulate on
trigger_data_free_list, later frees fall back to synchronously freeing
only the current object, and the older queued entries are leaked
forever.</p>
<p>To trigger this, add the following to the kernel command line:</p>
<p>trace_event=sched_switch trace_trigger=sched_switch.traceon,sched_switch.traceon</p>
<p>The second traceon trigger will fail and be freed. This triggers a NULL
pointer dereference and crashes the kernel.</p>
<p>Keep the deferred boot-time behavior, but when kthread creation fails,
drain the whole queued list synchronously. Do the same in the late-init
drain path so queued entries are not stranded there either.</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-31481"/>
  </entry>
</feed>
