<?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 11:29:40 +0000</lastBuildDate>
    <item>
      <title>CVE-2024-50187 — drm/vc4: Stop the active perfmon before being destroyed</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2024-50187</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;drm/vc4: Stop the active perfmon before being destroyed&lt;/p&gt;
&lt;p&gt;Upon closing the file descriptor, the active performance monitor is not
stopped. Although all perfmons are destroyed in `vc4_perfmon_close_file()`,
the active performance monitor&amp;#39;s pointer (`vc4-&amp;gt;active_perfmon`) is still
retained.&lt;/p&gt;
&lt;p&gt;If we open a new file descriptor and submit a few jobs with performance
monitors, the driver will attempt to stop the active performance monitor
using the stale pointer in `vc4-&amp;gt;active_perfmon`. However, this pointer
is no longer valid because the previous process has already terminated,
and all performance monitors associated with it have been destroyed and
freed.&lt;/p&gt;
&lt;p&gt;To fix this, when the active performance monitor belongs to a given
process, explicitly stop it before destroying and freeing 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;drm/vc4: Stop the active perfmon before being destroyed&lt;/p&gt;
&lt;p&gt;Upon closing the file descriptor, the active performance monitor is not
stopped. Although all perfmons are destroyed in `vc4_perfmon_close_file()`,
the active performance monitor&amp;#39;s pointer (`vc4-&amp;gt;active_perfmon`) is still
retained.&lt;/p&gt;
&lt;p&gt;If we open a new file descriptor and submit a few jobs with performance
monitors, the driver will attempt to stop the active performance monitor
using the stale pointer in `vc4-&amp;gt;active_perfmon`. However, this pointer
is no longer valid because the previous process has already terminated,
and all performance monitors associated with it have been destroyed and
freed.&lt;/p&gt;
&lt;p&gt;To fix this, when the active performance monitor belongs to a given
process, explicitly stop it before destroying and freeing it.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2024-50187</guid>
    </item>
  </channel>
</rss>
