<?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>Thu, 01 Oct 2026 16:12:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-46309 — drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-46309</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise&lt;/p&gt;
&lt;p&gt;Add validation in xe_vm_madvise_ioctl() to reject PAT indices with
XE_COH_NONE coherency mode when applied to CPU cached memory.&lt;/p&gt;
&lt;p&gt;Using coh_none with CPU cached buffers is a security issue. When the
kernel clears pages before reallocation, the clear operation stays in
CPU cache (dirty). GPU with coh_none can bypass CPU caches and read
stale sensitive data directly from DRAM, potentially leaking data from
previously freed pages of other processes.&lt;/p&gt;
&lt;p&gt;This aligns with the existing validation in vm_bind path
(xe_vm_bind_ioctl_validate_bo).&lt;/p&gt;
&lt;p&gt;v2(Matthew brost)
- Add fixes
- Move one debug print to better place&lt;/p&gt;
&lt;p&gt;v3(Matthew Auld)
- Should be drm/xe/uapi
- More Cc&lt;/p&gt;
&lt;p&gt;v4(Shuicheng Lin)
- Fix kmem leak issues by the way&lt;/p&gt;
&lt;p&gt;v5
- Remove kmem leak because it has been merged by another patch&lt;/p&gt;
&lt;p&gt;v6
- Remove the fix which is not related to current fix&lt;/p&gt;
&lt;p&gt;v7
- No change&lt;/p&gt;
&lt;p&gt;v8
- Rebase&lt;/p&gt;
&lt;p&gt;v9
- Limit the restrictions to iGPU&lt;/p&gt;
&lt;p&gt;v10
- No change&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 016ccdb674b8c899940b3944952c96a6a490d10a)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Linux, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9&lt;/p&gt;
&lt;p&gt;In the Linux kernel, the following vulnerability has been resolved:&lt;/p&gt;
&lt;p&gt;drm/xe/uapi: Reject coh_none PAT index for CPU cached memory in madvise&lt;/p&gt;
&lt;p&gt;Add validation in xe_vm_madvise_ioctl() to reject PAT indices with
XE_COH_NONE coherency mode when applied to CPU cached memory.&lt;/p&gt;
&lt;p&gt;Using coh_none with CPU cached buffers is a security issue. When the
kernel clears pages before reallocation, the clear operation stays in
CPU cache (dirty). GPU with coh_none can bypass CPU caches and read
stale sensitive data directly from DRAM, potentially leaking data from
previously freed pages of other processes.&lt;/p&gt;
&lt;p&gt;This aligns with the existing validation in vm_bind path
(xe_vm_bind_ioctl_validate_bo).&lt;/p&gt;
&lt;p&gt;v2(Matthew brost)
- Add fixes
- Move one debug print to better place&lt;/p&gt;
&lt;p&gt;v3(Matthew Auld)
- Should be drm/xe/uapi
- More Cc&lt;/p&gt;
&lt;p&gt;v4(Shuicheng Lin)
- Fix kmem leak issues by the way&lt;/p&gt;
&lt;p&gt;v5
- Remove kmem leak because it has been merged by another patch&lt;/p&gt;
&lt;p&gt;v6
- Remove the fix which is not related to current fix&lt;/p&gt;
&lt;p&gt;v7
- No change&lt;/p&gt;
&lt;p&gt;v8
- Rebase&lt;/p&gt;
&lt;p&gt;v9
- Limit the restrictions to iGPU&lt;/p&gt;
&lt;p&gt;v10
- No change&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 016ccdb674b8c899940b3944952c96a6a490d10a)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-46309</guid>
    </item>
  </channel>
</rss>
