<?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://db.gcve.eu</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, 03 Nov 2026 21:51:57 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-98779 — drm/amdgpu: fix ACP MFD device leak on init failure</title>
      <link>https://db.gcve.eu/vuln/cve-2026-98779</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/amdgpu: fix ACP MFD device leak on init failure&lt;/p&gt;
&lt;p&gt;acp_hw_init() registers ACP child devices with mfd_add_devices() before
attaching them to the ACP power domain and initializing the hardware.&lt;/p&gt;
&lt;p&gt;If attaching a child to the power domain fails, or if the ACP reset or
clock enable operation times out, the failure path frees only the
source cell, resource, and platform-data allocations. The child
platform devices already registered by mfd_add_devices() remain
registered and are never released.&lt;/p&gt;
&lt;p&gt;Remove the children from the power domain and unregister the MFD
devices on failures that occur after mfd_add_devices() succeeds. Keep
mfd_add_devices() failures on the existing cleanup path since the MFD
core already rolls back partially registered children itself.&lt;/p&gt;
&lt;p&gt;The issue was identified by a static analysis tool I developed and
confirmed by manual review.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)&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/amdgpu: fix ACP MFD device leak on init failure&lt;/p&gt;
&lt;p&gt;acp_hw_init() registers ACP child devices with mfd_add_devices() before
attaching them to the ACP power domain and initializing the hardware.&lt;/p&gt;
&lt;p&gt;If attaching a child to the power domain fails, or if the ACP reset or
clock enable operation times out, the failure path frees only the
source cell, resource, and platform-data allocations. The child
platform devices already registered by mfd_add_devices() remain
registered and are never released.&lt;/p&gt;
&lt;p&gt;Remove the children from the power domain and unregister the MFD
devices on failures that occur after mfd_add_devices() succeeds. Keep
mfd_add_devices() failures on the existing cleanup path since the MFD
core already rolls back partially registered children itself.&lt;/p&gt;
&lt;p&gt;The issue was identified by a static analysis tool I developed and
confirmed by manual review.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 63da68d6a2279ec945581c990c5a59a5ae8b5560)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-98779</guid>
    </item>
  </channel>
</rss>
