GHSA-9MXH-X95W-JRRC
Vulnerability from github – Published: 2026-10-23 15:31 – Updated: 2026-10-23 15:31In the Linux kernel, the following vulnerability has been resolved:
drm/amdgpu/userq: only accept doorbell BOs as queue doorbell
amdgpu_userq_get_doorbell_index() pins any BO passed as doorbell_handle into the doorbell domain. For a regular BO, TTM moves it with ttm_bo_move_null() and its contents are lost. Since an importer on the same device gets the exporter's GEM object, a client can do this to a buffer another client shared with it.
Reject BOs that were not created in the doorbell domain.
v2: drop the error message, use a local abo variable (Christian)
(cherry picked from commit f7497bbc19db4821c62b9d97b31c9086feb2d917)
{
"affected": [],
"aliases": [
"CVE-2026-98997"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-10-23T13:17:21Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdgpu/userq: only accept doorbell BOs as queue doorbell\n\namdgpu_userq_get_doorbell_index() pins any BO passed as doorbell_handle\ninto the doorbell domain. For a regular BO, TTM moves it with\nttm_bo_move_null() and its contents are lost. Since an importer on the\nsame device gets the exporter\u0027s GEM object, a client can do this to a\nbuffer another client shared with it.\n\nReject BOs that were not created in the doorbell domain.\n\nv2: drop the error message, use a local abo variable (Christian)\n\n(cherry picked from commit f7497bbc19db4821c62b9d97b31c9086feb2d917)",
"id": "GHSA-9mxh-x95w-jrrc",
"modified": "2026-10-23T15:31:34Z",
"published": "2026-10-23T15:31:34Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-98997"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/112dbe2b10d6d088a6c599980dd960dcbfa55ff0"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/7f7c88dbf4d543f6703e53bdeed380e886733167"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/8640b3f961d743d6dc0458c2b53a3af434690cc1"
}
],
"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.