Menu

Star on GitHub · 3.2k

CVE-2025-21939

7.8 · HIGH

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 t…

Published Apr 1, 2025CWE-476EPSS 0.21%

Overview

CVE-2025-21939 is a high-severity vulnerability. It was published on April 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical 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 derefe

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-21939?

CVE-2025-21939 is a high-severity vulnerability. It was published on April 1, 2025 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2025-21939?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2025-21939?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-21939?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-21939 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all