GHSA-WRF7-G73G-GR9R
Vulnerability from github – Published: 2026-10-28 12:31 – Updated: 2026-10-28 12:31In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: actually validate userq BOs
This was supposed to loop over the individual evicted list, as the kernel and always_valid evicted lists were already handled in amdgpu_vm_validate.
Without this, BOs that were created and evicted before a userq was made would never end up in an eviction fence rearm.
Also add the missing ref to the BO before drm_exec locks and refs it.
(cherry picked from commit 18decfc9e8cc0fa70b6de9944cc27a37729edfbd)
{
"affected": [],
"aliases": [
"CVE-2026-99119"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-28T11:17:31Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/userq: actually validate userq BOs\n\nThis was supposed to loop over the individual evicted list, as the\nkernel and always_valid evicted lists were already handled in\namdgpu_vm_validate.\n\nWithout this, BOs that were created and evicted before a userq was made\nwould never end up in an eviction fence rearm.\n\nAlso add the missing ref to the BO before drm_exec locks and refs it.\n\n(cherry picked from commit 18decfc9e8cc0fa70b6de9944cc27a37729edfbd)",
"id": "GHSA-wrf7-g73g-gr9r",
"modified": "2026-10-28T12:31:03Z",
"published": "2026-10-28T12:31:03Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-99119"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/32d0771ef4ca69c30a1db3aefa34dd177cd2a047"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/d1d6b859e89dd274cd0fae77503cdf91be8310c0"
}
],
"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.