<?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-29T03:13:27.481400+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-2025-71099</id>
    <title>CVE-2025-71099 — drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()</title>
    <updated>2026-09-29T03:13:27.591800+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/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()</p>
<p>In xe_oa_add_config_ioctl(), we accessed oa_config-&gt;id after dropping
metrics_lock. Since this lock protects the lifetime of oa_config, an
attacker could guess the id and call xe_oa_remove_config_ioctl() with
perfect timing, freeing oa_config before we dereference it, leading to
a potential use-after-free.</p>
<p>Fix this by caching the id in a local variable while holding the lock.</p>
<p>v2: (Matt A)
- Dropped mutex_unlock(&amp;oa-&gt;metrics_lock) ordering change from
  xe_oa_remove_config_ioctl()</p>
<p>(cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2025-71099"/>
  </entry>
</feed>
