CVE-2025-71301: drm/tests: shmem: Hold reservation lock around vmap/vunmap
In the Linux kernel, the following vulnerability has been resolved:
drm/tests: shmem: Hold reservation lock around vmap/vunmap
Acquire and release the GEM object's reservation lock around vmap and vunmap operations. The tests use vmaplocked, which led to errors such as show below.
[ 122.292030] WARNING: CPU: 3 PID: 1413 at drivers/gpu/drm/drmgemshmemhelper.c:390 drmgemshmemvmaplocked+0x3a3/0x6f0
[ 122.468066] WARNING: CPU: 3 PID: 1413 at drivers/gpu/drm/drmgemshmemhelper.c:293 drmgemshmempinlocked+0x1fe/0x350
[ 122.563504] WARNING: CPU: 3 PID: 1413 at drivers/gpu/drm/drmgemshmemhelper.c:234 drmgemshmemgetpageslocked+0x23c/0x370
[ 122.662248] WARNING: CPU: 2 PID: 1413 at drivers/gpu/drm/drmgemshmemhelper.c:452 drmgemshmemvunmaplocked+0x101/0x330
Only export the new vmap/vunmap helpers for Kunit tests. These are not interfaces for regular drivers.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-71301?
CVE-2025-71301 has a medium severity rating due to its potential impact on the Linux kernel's resource management.
How do I fix CVE-2025-71301?
To fix CVE-2025-71301, update to the latest version of the Linux kernel where the vulnerability has been patched.
What types of systems are affected by CVE-2025-71301?
CVE-2025-71301 affects systems running specific versions of the Linux kernel that utilize DRM testing with shmem.
What impact does CVE-2025-71301 have?
The impact of CVE-2025-71301 may include potential resource management issues while using vmap and vunmap operations in the Linux kernel.
Is CVE-2025-71301 exploitable remotely?
CVE-2025-71301 is not considered remotely exploitable as it primarily concerns local operations in the Linux kernel.