CVE-2025-40339
Description
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: fix nullptr err of vm_handle_moved
If a amdgpu_bo_va is fpriv->prt_va, the bo of this one is always NULL. So, such kind of amdgpu_bo_va should be updated separately before amdgpu_vm_handle_moved.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
A null pointer dereference in the Linux kernel's amdgpu driver occurs when handling moved virtual memory for a private virtual address without a backing buffer object.
Vulnerability
Overview
In the Linux kernel's amdgpu DRM driver, a null pointer dereference vulnerability exists in the amdgpu_vm_handle_moved function. The root cause is that when an amdgpu_bo_va structure corresponds to the private virtual address (fpriv->prt_va), its bo (buffer object) pointer is always NULL. The code previously did not account for this special case, leading to a NULL pointer dereference when attempting to access the bo field during page table update processing [1].
Exploitation
Conditions
To exploit this vulnerability, an attacker would need local access to the system and the ability to trigger the code path that processes moved virtual memory for a private virtual address. This typically requires performing GPU operations that cause page table updates, such as memory mapping or buffer migration. No special privileges beyond local user access are required, as the driver is accessible from user space via the Direct Rendering Manager (DRM) interface.
Impact
A successful exploit of this null pointer dereference can lead to a kernel crash (denial of service). In some cases, if an attacker can control the memory layout, it might be possible to achieve privilege escalation by exploiting the resulting kernel panic or by corrupting kernel memory. The vulnerability is classified as a high-severity issue due to the potential for system instability and local privilege escalation.
Mitigation
The fix has been applied in the Linux kernel stable tree via commit 47281febebe337586569aa4c5694a7511063a42e [1]. Users are advised to update their kernel to a version that includes this patch. No workaround is available; updating the kernel is the recommended mitigation.
AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
2Patches
347281febebe3273d1ea12e42859958a7faefVulnerability mechanics
Generated on May 9, 2026. Inputs: CWE entries + fix-commit diffs from this CVE's patches. Citations validated against bundle.
References
3News mentions
0No linked articles in our index yet.