CVE-2026-68275: drm/amdgpu: check amdgpu_vm_bo_find() result in GET_MAPPING_INFO
In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu: check amdgpuvmbofind() result in GETMAPPINGINFO
The AMDGPUGEMOPGETMAPPINGINFO path of amdgpugemopioctl() looks up the bova for the buffer object in the caller's VM via amdgpuvmbofind(), but uses the returned pointer without checking it.
amdgpuvmbofind() returns NULL when the BO has no bova in that VM, which is the normal case for a BO that has never been mapped. The result is fed straight into amdgpuvmbovaforeachvalidmapping(), which expands to listforeachentry(mapping, &(bova)->valids, list) and dereferences bova, causing a NULL pointer dereference.
This is reachable by any process able to issue the ioctl (render group) simply by requesting mapping info for an unmapped BO.
Return -ENOENT when no bova is found, jumping to outexec so the drmexec context and GEM object reference are released.
(cherry picked from commit 528b19377affc1cc7362a70a254c1dda793595f9)
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68275?
The severity of CVE-2026-68275 is rated at risk level 29.
How do I fix CVE-2026-68275?
To fix CVE-2026-68275, you should update your Linux kernel to the latest version where the vulnerability has been patched.
What impact does CVE-2026-68275 have on system security?
CVE-2026-68275 may lead to a null pointer dereference, potentially causing system crashes and denial of service.
Is CVE-2026-68275 related to AMD graphics drivers?
Yes, CVE-2026-68275 is specifically related to the AMDGPU driver in the Linux kernel.
When was CVE-2026-68275 published?
CVE-2026-68275 was published on August 10, 2026.