<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 03:06:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-68175 — tracing: Fix resource leak on mmiotrace trace_pipe close</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-68175</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: Fix resource leak on mmiotrace trace_pipe close&lt;/p&gt;
&lt;p&gt;The mmiotrace tracer was added May 12th 2008. At that time, resources
created in pipe_open() could not be freed because there was not
pipe_close function pointer of the tracer. The pipe_close function pointer
was added in December 7th, 2009, but the mmiotrace tracer was not updated.&lt;/p&gt;
&lt;p&gt;mmio_pipe_open() allocates a header_iter and takes a pci_dev reference
when trace_pipe is opened. mmio_close() frees them, but it was only
wired to the tracer&amp;#39;s .close callback.&lt;/p&gt;
&lt;p&gt;tracing_release_pipe() invokes .pipe_close, not .close, when the
trace_pipe file is released. As a result, closing trace_pipe with the
mmiotrace tracer active leaked the header_iter allocation and left a
stale pci_dev reference.&lt;/p&gt;
&lt;p&gt;Set .pipe_close to mmio_close, matching how function_graph wires both
callbacks to the same handler.&lt;/p&gt;
&lt;p&gt;Note, if the trace_pipe is read to completion, it will clean up the
resources, but if one were to run:&lt;/p&gt;
&lt;p&gt;# head -n 1 /sys/kernel/tracing/trace_pipe
 VERSION 20070824&lt;/p&gt;
&lt;p&gt;Over and over again, it would trigger a massive leak.&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: Fix resource leak on mmiotrace trace_pipe close&lt;/p&gt;
&lt;p&gt;The mmiotrace tracer was added May 12th 2008. At that time, resources
created in pipe_open() could not be freed because there was not
pipe_close function pointer of the tracer. The pipe_close function pointer
was added in December 7th, 2009, but the mmiotrace tracer was not updated.&lt;/p&gt;
&lt;p&gt;mmio_pipe_open() allocates a header_iter and takes a pci_dev reference
when trace_pipe is opened. mmio_close() frees them, but it was only
wired to the tracer&amp;#39;s .close callback.&lt;/p&gt;
&lt;p&gt;tracing_release_pipe() invokes .pipe_close, not .close, when the
trace_pipe file is released. As a result, closing trace_pipe with the
mmiotrace tracer active leaked the header_iter allocation and left a
stale pci_dev reference.&lt;/p&gt;
&lt;p&gt;Set .pipe_close to mmio_close, matching how function_graph wires both
callbacks to the same handler.&lt;/p&gt;
&lt;p&gt;Note, if the trace_pipe is read to completion, it will clean up the
resources, but if one were to run:&lt;/p&gt;
&lt;p&gt;# head -n 1 /sys/kernel/tracing/trace_pipe
 VERSION 20070824&lt;/p&gt;
&lt;p&gt;Over and over again, it would trigger a massive leak.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-68175</guid>
    </item>
  </channel>
</rss>
