<?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>Sat, 07 Nov 2026 10:44:16 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-99150 — drm/amdgpu: don't drop the runtime PM reference twice in amdgpu_gpr</title>
      <link>https://db.gcve.eu/vuln/cve-2026-99150</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: don&amp;#39;t drop the runtime PM reference twice in amdgpu_gpr&lt;/p&gt;
&lt;p&gt;amdgpu_debugfs_gpr_read() drops its runtime PM reference right after
reading the wave registers. When copying them to userspace fails, it
jumps to the err label, which drops the reference a second time. A read
into a bad buffer on Navi31 either steals a reference somebody else
holds (power/runtime_usage goes from 1 to 0) or underflows the count:&lt;/p&gt;
&lt;p&gt;amdgpu 0000:03:00.0: Runtime PM usage count underflow!&lt;/p&gt;
&lt;p&gt;The registers are already in the kernel buffer at that point, so finish
the hardware access first and copy the buffer with a single
copy_to_user() instead of the put_user() loop with its own error path.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)&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: don&amp;#39;t drop the runtime PM reference twice in amdgpu_gpr&lt;/p&gt;
&lt;p&gt;amdgpu_debugfs_gpr_read() drops its runtime PM reference right after
reading the wave registers. When copying them to userspace fails, it
jumps to the err label, which drops the reference a second time. A read
into a bad buffer on Navi31 either steals a reference somebody else
holds (power/runtime_usage goes from 1 to 0) or underflows the count:&lt;/p&gt;
&lt;p&gt;amdgpu 0000:03:00.0: Runtime PM usage count underflow!&lt;/p&gt;
&lt;p&gt;The registers are already in the kernel buffer at that point, so finish
the hardware access first and copy the buffer with a single
copy_to_user() instead of the put_user() loop with its own error path.&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 31035bbd74f7c3e10c163db875b8e67f8b50ee6a)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-99150</guid>
    </item>
  </channel>
</rss>
