<?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>Mon, 28 Sep 2026 21:22:01 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-68376 — coresight: ETR: Fix ETR buffer use-after-free issue</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-68376</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;coresight: ETR: Fix ETR buffer use-after-free issue&lt;/p&gt;
&lt;p&gt;When ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed
and enabled again, currently sysfs_buf will point to the newly
allocated memory(buf_new) and free the old memory(buf_old). But the
etr_buf that is being used by the ETR remains pointed to buf_old, not
updated to buf_new. In this case, it will result in a memory
use-after-free issue.&lt;/p&gt;
&lt;p&gt;Fix this by checking ETR&amp;#39;s mode before updating and releasing buf_old,
if the mode is CS_MODE_SYSFS, then skip updating and releasing it.&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;coresight: ETR: Fix ETR buffer use-after-free issue&lt;/p&gt;
&lt;p&gt;When ETR is enabled as CS_MODE_SYSFS, if the buffer size is changed
and enabled again, currently sysfs_buf will point to the newly
allocated memory(buf_new) and free the old memory(buf_old). But the
etr_buf that is being used by the ETR remains pointed to buf_old, not
updated to buf_new. In this case, it will result in a memory
use-after-free issue.&lt;/p&gt;
&lt;p&gt;Fix this by checking ETR&amp;#39;s mode before updating and releasing buf_old,
if the mode is CS_MODE_SYSFS, then skip updating and releasing it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-68376</guid>
    </item>
  </channel>
</rss>
