<?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-29T08:43:37.647289+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-68245</id>
    <title>CVE-2026-68245 — drm/amdgpu: fix lifetime issue of amdgpu_vm_get_task_info_pasid()</title>
    <updated>2026-09-29T08:43:37.665359+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 lifetime issue of amdgpu_vm_get_task_info_pasid()</p>
<p>The vm pointer returned from amdgpu_vm_get_vm_from_pasid() is only
valid while the lock is still being held. Once xa_unlock_irqrestore is
called and returned, the pointer is no longer under lock and is subject
to modification. Since, the caller still dereferences vm-&gt;task_info in
amdgpu_vm_get_task_info_vm() after the lock is removed, this causes a
use after unlock problem.</p>
<p>Remove the lifetime issue present in amdgpu_vm_get_task_info_pasid()
through removing the amdgpu_vm_get_vm_from_pasid() function from
amdgpu_vm.c and making the relevant code inline to hold the lock while
it is still in use.</p>
<p>(cherry picked from commit 9d01579f3f868b333acc901815972685989092c7)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68245"/>
  </entry>
</feed>
