GHSA-634R-724X-3G6W
Vulnerability from github – Published: 2026-09-16 12:30 – Updated: 2026-09-16 12:30In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: fix scope of mqd_mgr dereference in pqm_debugfs_mqds
Reading /sys/kernel/debug/kfd/mqds while a process holds an active KFD queue triggers a NULL pointer dereference because the for loop that calls mqd_mgr->debugfs_show_mqd() is incorrectly placed outside the if (pqn->q) block that initializes mqd_mgr.
The queue list can contain entries where pqn->q is NULL (kernel queues where only pqn->kq is valid). In the original code:
if (pqn->q) { ... mqd_mgr = q->device->dqm->mqd_mgrs[mqd_type]; size = mqd_mgr->mqd_stride(...); }
for (xcc = 0; xcc < num_xccs; xcc++) { // WRONG: outside if block mqd = q->mqd + size * xcc; r = mqd_mgr->debugfs_show_mqd(m, mqd); }
When iterating over a queue node where pqn->q is NULL: 1. The if (pqn->q) block is skipped 2. mqd_mgr remains uninitialized (NULL from declaration) 3. The for loop executes anyway 4. mqd_mgr->debugfs_show_mqd(m, mqd) dereferences NULL
The crash manifests as:
BUG: kernel NULL pointer dereference, address: 0000000000000000 #PF: supervisor instruction fetch in kernel mode RIP: 0010:0x0 Call Trace: pqm_debugfs_mqds+0x10c/0x1d0 [amdgpu] kfd_debugfs_mqds_by_process+0x9b/0x110 [amdgpu] seq_read_iter+0x132/0x4b0 ...
Fix by moving the for loop inside the if (pqn->q) block, so mqd_mgr and related variables are only used when properly initialized.
(cherry picked from commit 8bfe29d5c798940f797aa24135d2734c3ffce9de)
{
"affected": [],
"aliases": [
"CVE-2026-89809"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-16T11:16:46Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amdkfd: fix scope of mqd_mgr dereference in pqm_debugfs_mqds\n\nReading /sys/kernel/debug/kfd/mqds while a process holds an active KFD\nqueue triggers a NULL pointer dereference because the for loop that\ncalls mqd_mgr-\u003edebugfs_show_mqd() is incorrectly placed outside the\nif (pqn-\u003eq) block that initializes mqd_mgr.\n\nThe queue list can contain entries where pqn-\u003eq is NULL (kernel queues\nwhere only pqn-\u003ekq is valid). In the original code:\n\n if (pqn-\u003eq) {\n ...\n mqd_mgr = q-\u003edevice-\u003edqm-\u003emqd_mgrs[mqd_type];\n size = mqd_mgr-\u003emqd_stride(...);\n }\n\n for (xcc = 0; xcc \u003c num_xccs; xcc++) { // WRONG: outside if block\n mqd = q-\u003emqd + size * xcc;\n r = mqd_mgr-\u003edebugfs_show_mqd(m, mqd);\n }\n\nWhen iterating over a queue node where pqn-\u003eq is NULL:\n1. The if (pqn-\u003eq) block is skipped\n2. mqd_mgr remains uninitialized (NULL from declaration)\n3. The for loop executes anyway\n4. mqd_mgr-\u003edebugfs_show_mqd(m, mqd) dereferences NULL\n\nThe crash manifests as:\n\n BUG: kernel NULL pointer dereference, address: 0000000000000000\n #PF: supervisor instruction fetch in kernel mode\n RIP: 0010:0x0\n Call Trace:\n pqm_debugfs_mqds+0x10c/0x1d0 [amdgpu]\n kfd_debugfs_mqds_by_process+0x9b/0x110 [amdgpu]\n seq_read_iter+0x132/0x4b0\n ...\n\nFix by moving the for loop inside the if (pqn-\u003eq) block, so mqd_mgr\nand related variables are only used when properly initialized.\n\n(cherry picked from commit 8bfe29d5c798940f797aa24135d2734c3ffce9de)",
"id": "GHSA-634r-724x-3g6w",
"modified": "2026-09-16T12:30:37Z",
"published": "2026-09-16T12:30:37Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89809"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/012a026bae0212952b423a842b7e2c0bf21f8e7a"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/58e866711b234571b0ce342c43d153a4786b32b8"
}
],
"schema_version": "1.4.0",
"severity": []
}
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.
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.