<?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 18:04:19 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-21939 — drm/xe/hmm: Don't dereference struct page pointers without notifier lock</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2025-21939</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/hmm: Don&amp;#39;t dereference struct page pointers without notifier lock&lt;/p&gt;
&lt;p&gt;The pnfs that we obtain from hmm_range_fault() point to pages that
we don&amp;#39;t have a reference on, and the guarantee that they are still
in the cpu page-tables is that the notifier lock must be held and the
notifier seqno is still valid.&lt;/p&gt;
&lt;p&gt;So while building the sg table and marking the pages accesses / dirty
we need to hold this lock with a validated seqno.&lt;/p&gt;
&lt;p&gt;However, the lock is reclaim tainted which makes
sg_alloc_table_from_pages_segment() unusable, since it internally
allocates memory.&lt;/p&gt;
&lt;p&gt;Instead build the sg-table manually. For the non-iommu case
this might lead to fewer coalesces, but if that&amp;#39;s a problem it can
be fixed up later in the resource cursor code. For the iommu case,
the whole sg-table may still be coalesced to a single contigous
device va region.&lt;/p&gt;
&lt;p&gt;This avoids marking pages that we don&amp;#39;t own dirty and accessed, and
it also avoid dereferencing struct pages that we don&amp;#39;t own.&lt;/p&gt;
&lt;p&gt;v2:
- Use assert to check whether hmm pfns are valid (Matthew Auld)
- Take into account that large pages may cross range boundaries
  (Matthew Auld)&lt;/p&gt;
&lt;p&gt;v3:
- Don&amp;#39;t unnecessarily check for a non-freed sg-table. (Matthew Auld)
- Add a missing up_read() in an error path. (Matthew Auld)&lt;/p&gt;
&lt;p&gt;(cherry picked from commit ea3e66d280ce2576664a862693d1da8fd324c317)&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/hmm: Don&amp;#39;t dereference struct page pointers without notifier lock&lt;/p&gt;
&lt;p&gt;The pnfs that we obtain from hmm_range_fault() point to pages that
we don&amp;#39;t have a reference on, and the guarantee that they are still
in the cpu page-tables is that the notifier lock must be held and the
notifier seqno is still valid.&lt;/p&gt;
&lt;p&gt;So while building the sg table and marking the pages accesses / dirty
we need to hold this lock with a validated seqno.&lt;/p&gt;
&lt;p&gt;However, the lock is reclaim tainted which makes
sg_alloc_table_from_pages_segment() unusable, since it internally
allocates memory.&lt;/p&gt;
&lt;p&gt;Instead build the sg-table manually. For the non-iommu case
this might lead to fewer coalesces, but if that&amp;#39;s a problem it can
be fixed up later in the resource cursor code. For the iommu case,
the whole sg-table may still be coalesced to a single contigous
device va region.&lt;/p&gt;
&lt;p&gt;This avoids marking pages that we don&amp;#39;t own dirty and accessed, and
it also avoid dereferencing struct pages that we don&amp;#39;t own.&lt;/p&gt;
&lt;p&gt;v2:
- Use assert to check whether hmm pfns are valid (Matthew Auld)
- Take into account that large pages may cross range boundaries
  (Matthew Auld)&lt;/p&gt;
&lt;p&gt;v3:
- Don&amp;#39;t unnecessarily check for a non-freed sg-table. (Matthew Auld)
- Add a missing up_read() in an error path. (Matthew Auld)&lt;/p&gt;
&lt;p&gt;(cherry picked from commit ea3e66d280ce2576664a862693d1da8fd324c317)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/cve-2025-21939</guid>
    </item>
  </channel>
</rss>
