Menu

Star on GitHub · 3.2k

CVE-2026-68275

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: check amdgpu_vm_bo_find() result in GET_MAPPING_INFO The AMDGPU_GEM_OP_GET_MAPPING_INFO path of amdgpu_gem_op_ioctl…

Published Aug 10, 2026EPSS 0.17%

Overview

CVE-2026-68275 is a known-severity vulnerability. It was published on August 10, 2026.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdgpu: check amdgpu_vm_bo_find() result in GET_MAPPING_INFO

The AMDGPU_GEM_OP_GET_MAPPING_INFO path of amdgpu_gem_op_ioctl() looks

up the bo_va for the buffer object in the caller's VM via

amdgpu_vm_bo_find(), but uses the returned pointer without checking it.

amdgpu_vm_bo_find() returns NULL when the BO has no bo_va in that VM,

which is the normal case for a BO that has never been mapped. The result

is fed straight into amdgpu_vm_bo_va_for_each_valid_mapping(), which

expands to list_for_each_entry(mapping, &(bo_va)->valids, list) and

dereferences bo_va, 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 bo_va is found, jumping to out_exec so the

drm_exec context and GEM object reference are released.

(cherry picked from commit 528b19377affc1cc7362a70a254c1dda793595f9)

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-2026-68275?

CVE-2026-68275 is a known-severity vulnerability. It was published on August 10, 2026.

How severe is CVE-2026-68275?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

How do I fix or remediate CVE-2026-68275?

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-2026-68275?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2026-68275 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.