<?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://vulnerability.circl.lu</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>Tue, 29 Sep 2026 03:13:28 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-71099 — drm/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-71099</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/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()&lt;/p&gt;
&lt;p&gt;In xe_oa_add_config_ioctl(), we accessed oa_config-&amp;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.&lt;/p&gt;
&lt;p&gt;Fix this by caching the id in a local variable while holding the lock.&lt;/p&gt;
&lt;p&gt;v2: (Matt A)
- Dropped mutex_unlock(&amp;amp;oa-&amp;gt;metrics_lock) ordering change from
  xe_oa_remove_config_ioctl()&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31)&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/xe/oa: Fix potential UAF in xe_oa_add_config_ioctl()&lt;/p&gt;
&lt;p&gt;In xe_oa_add_config_ioctl(), we accessed oa_config-&amp;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.&lt;/p&gt;
&lt;p&gt;Fix this by caching the id in a local variable while holding the lock.&lt;/p&gt;
&lt;p&gt;v2: (Matt A)
- Dropped mutex_unlock(&amp;amp;oa-&amp;gt;metrics_lock) ordering change from
  xe_oa_remove_config_ioctl()&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 28aeaed130e8e587fd1b73b6d66ca41ccc5a1a31)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-71099</guid>
    </item>
  </channel>
</rss>
