<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://vulnerability.circl.lu/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-09-30T17:50:29.133490+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>info@circl.lu</email>
  </author>
  <link href="https://vulnerability.circl.lu" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://vulnerability.circl.lu/vuln/cve-2026-53293</id>
    <title>CVE-2026-53293 — drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG</title>
    <updated>2026-09-30T17:50:29.135314+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Linux</p>
<p>In the Linux kernel, the following vulnerability has been resolved:</p>
<p>drm/amdgpu: fix AMDGPU_INFO_READ_MMR_REG</p>
<p>There were multiple issues in that code.</p>
<p>First of all the order between the reset semaphore and the mm_lock was
wrong (e.g. copy_to_user) was called while holding the lock.</p>
<p>Then we allocated memory while holding the reset semaphore which is also
a pretty big bug and can deadlock.</p>
<p>Then we used down_read_trylock() instead of waiting for the reset to
finish.</p>
<p>(cherry picked from commit 361b6e6b303d4b691f6c5974d3eaab67ca6dd90e)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-53293"/>
  </entry>
</feed>
