<?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-10-01T07:03:45.012987+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-46311</id>
    <title>CVE-2026-46311 — drm/amdgpu/userq: fix access to stale wptr mapping</title>
    <updated>2026-10-01T07:03:45.864428+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/userq: fix access to stale wptr mapping</p>
<p>Use drm_exec to take both locks i.e vm root bo and
wptr_obj bo to access the mapping data properly.</p>
<p>This fixes the security issue of unmap the wptr_obj while
a queue creation is in progress and passing other
bo at same address.</p>
<p>(cherry picked from commit 1fc6c8ab45dbee096469c08c13f6099d57a52d6c)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-46311"/>
  </entry>
</feed>
