CVE-2025-71296: drm/tests: shmem: Hold reservation lock around purge
In the Linux kernel, the following vulnerability has been resolved:
drm/tests: shmem: Hold reservation lock around purge
Acquire and release the GEM object's reservation lock around calls to the object's purge operation. The tests use drmgemshmempurgelocked(), which led to errors such as show below.
[ 58.709128] WARNING: CPU: 1 PID: 1354 at drivers/gpu/drm/drmgemshmemhelper.c:515 drmgemshmempurgelocked+0x51c/0x740
Only export the new helper drmgemshmempurge() for Kunit tests. This is not an interface for regular drivers.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Compensating control
Acquire the GEM object's reservation lock before calling drm_gem_shmem_purge_locked() or the purge operation, and release the lock afterward.
- Compensating control
Export the new drm_gem_shmem_purge() helper only for KUnit tests; do not expose it as an interface for regular drivers.
Event History
Frequently Asked Questions
What is the severity of CVE-2025-71296?
CVE-2025-71296 has been classified as a moderate severity vulnerability in the Linux kernel.
How do I fix CVE-2025-71296?
To fix CVE-2025-71296, ensure that you update to the latest patched version of the Linux kernel.
What types of systems are affected by CVE-2025-71296?
CVE-2025-71296 affects systems running vulnerable versions of the Linux kernel that utilize the Direct Rendering Manager.
Can CVE-2025-71296 be exploited remotely?
CVE-2025-71296 is primarily a local privilege escalation vulnerability and is not typically exploitable remotely.
What components of the Linux kernel are involved in CVE-2025-71296?
CVE-2025-71296 specifically involves the GEM object's reservation lock in the Direct Rendering Manager testing framework.