<?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-29T13:03:39.069202+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-68265</id>
    <title>CVE-2026-68265 — drm/xe/vm: Fix BO prefetch with CONSULT_MEM_ADVISE_PREF_LOC</title>
    <updated>2026-09-29T13:03:39.142724+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/vm: Fix BO prefetch with CONSULT_MEM_ADVISE_PREF_LOC</p>
<p>When prefetch region is DRM_XE_CONSULT_MEM_ADVISE_PREF_LOC for a BO VMA,
the code used it as an index into region_to_mem_type[], causing an
out-of-bounds access since the value is -1.</p>
<p>Resolve the preferred location for BO VMAs directly: local VRAM on dGFX
(using the BO's tile placement) or system memory on iGPU.</p>
<p>Discovered using AI-assisted static analysis confirmed by Intel Product
Security.</p>
<p>v2:
-Fix null dereference</p>
<p>(cherry picked from commit d9a4906ac03be9f6ed3f3b45c56c866b867fd75b)</p></div>
    </content>
    <link href="https://vulnerability.circl.lu/vuln/cve-2026-68265"/>
  </entry>
</feed>
