Menu

Star on GitHub · 3.2k

CVE-2026-72327

In the Linux kernel, the following vulnerability has been resolved: drm/v3d: Reject invalid indirect BO handle in indirect CSD setup v3d_get_cpu_indirect_csd_params() looks up the indirect buffer…

Published Aug 15, 2026EPSS 0.21%

Overview

CVE-2026-72327 is a known-severity vulnerability. It was published on August 15, 2026.

Technical description

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

drm/v3d: Reject invalid indirect BO handle in indirect CSD setup

v3d_get_cpu_indirect_csd_params() looks up the indirect buffer object

from a userspace-supplied handle but never checks the result. A bogus

or stale handle makes drm_gem_object_lookup() return NULL, which is

then stored in info->indirect and only dereferenced later when the

indirect CSD job runs, turning a userspace mistake into a NULL pointer

dereference in the kernel.

Bail out with -ENOENT as soon as the lookup fails, so the bad handle is

rejected at submission time.

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-72327?

CVE-2026-72327 is a known-severity vulnerability. It was published on August 15, 2026.

How severe is CVE-2026-72327?

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-72327?

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-72327?

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