GHSA-XPVH-XVQ6-7MJQ
Vulnerability from github – Published: 2026-08-15 06:32 – Updated: 2026-08-15 06:32In 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.
{
"affected": [],
"aliases": [
"CVE-2026-72327"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-08-15T06:22:05Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/v3d: Reject invalid indirect BO handle in indirect CSD setup\n\nv3d_get_cpu_indirect_csd_params() looks up the indirect buffer object\nfrom a userspace-supplied handle but never checks the result. A bogus\nor stale handle makes drm_gem_object_lookup() return NULL, which is\nthen stored in info-\u003eindirect and only dereferenced later when the\nindirect CSD job runs, turning a userspace mistake into a NULL pointer\ndereference in the kernel.\n\nBail out with -ENOENT as soon as the lookup fails, so the bad handle is\nrejected at submission time.",
"id": "GHSA-xpvh-xvq6-7mjq",
"modified": "2026-08-15T06:32:20Z",
"published": "2026-08-15T06:32:20Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-72327"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/2f8b8593c7832fad655290cef9e99af05b1b52b3"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/5d65dade4d84913d1879f3db6a12ac007e08314b"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/762116dfa72865c82151970960f7cf34f44b21c8"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7c27f630dc78b673e136cab7d410399a1c52146a"
}
],
"schema_version": "1.4.0",
"severity": []
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.