<?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>Sat, 03 Oct 2026 23:38:36 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-43280 — drm/xe: Add bounds check on pat_index to prevent OOB kernel read in madvise</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-43280</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: Add bounds check on pat_index to prevent OOB kernel read in madvise&lt;/p&gt;
&lt;p&gt;When user provides a bogus pat_index value through the madvise IOCTL, the
xe_pat_index_get_coh_mode() function performs an array access without
validating bounds. This allows a malicious user to trigger an out-of-bounds
kernel read from the xe-&amp;gt;pat.table array.&lt;/p&gt;
&lt;p&gt;The vulnerability exists because the validation in madvise_args_are_sane()
directly calls xe_pat_index_get_coh_mode(xe, args-&amp;gt;pat_index.val) without
first checking if pat_index is within [0, xe-&amp;gt;pat.n_entries).&lt;/p&gt;
&lt;p&gt;Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug
builds, it still performs the unsafe array access in production kernels.&lt;/p&gt;
&lt;p&gt;v2(Matthew Auld)
- Using array_index_nospec() to mitigate spectre attacks when the value
is used&lt;/p&gt;
&lt;p&gt;v3(Matthew Auld)
- Put the declarations at the start of the block&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)&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: Add bounds check on pat_index to prevent OOB kernel read in madvise&lt;/p&gt;
&lt;p&gt;When user provides a bogus pat_index value through the madvise IOCTL, the
xe_pat_index_get_coh_mode() function performs an array access without
validating bounds. This allows a malicious user to trigger an out-of-bounds
kernel read from the xe-&amp;gt;pat.table array.&lt;/p&gt;
&lt;p&gt;The vulnerability exists because the validation in madvise_args_are_sane()
directly calls xe_pat_index_get_coh_mode(xe, args-&amp;gt;pat_index.val) without
first checking if pat_index is within [0, xe-&amp;gt;pat.n_entries).&lt;/p&gt;
&lt;p&gt;Although xe_pat_index_get_coh_mode() has a WARN_ON to catch this in debug
builds, it still performs the unsafe array access in production kernels.&lt;/p&gt;
&lt;p&gt;v2(Matthew Auld)
- Using array_index_nospec() to mitigate spectre attacks when the value
is used&lt;/p&gt;
&lt;p&gt;v3(Matthew Auld)
- Put the declarations at the start of the block&lt;/p&gt;
&lt;p&gt;(cherry picked from commit 944a3329b05510d55c69c2ef455136e2fc02de29)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2026-43280</guid>
    </item>
  </channel>
</rss>
