GHSA-6FRH-MF5H-MGW9
Vulnerability from github – Published: 2026-09-11 21:31 – Updated: 2026-09-11 21:31In the Linux kernel, the following vulnerability has been resolved:
RDMA/uverbs: Guard legacy bundles without method_elm
The legacy write() path dispatches through a uverbs_api_write_method, but the uverbs_attr_bundle passed to provider code does not have an ioctl method element. If malformed provider input causes the common uverbs validation code to emit an error message, uverbs_get_handler_fn() dereferences the uninitialized method_elm pointer.
Initialize method_elm explicitly for legacy bundles and make uverbs_get_handler_fn() return NULL when no ioctl method is present. The legacy dispatcher continues to use its local write method, while the ioctl path continues to use the registered ioctl handler.
{
"affected": [],
"aliases": [
"CVE-2026-89505"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:32Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/uverbs: Guard legacy bundles without method_elm\n\nThe legacy write() path dispatches through a uverbs_api_write_method, but\nthe uverbs_attr_bundle passed to provider code does not have an ioctl\nmethod element. If malformed provider input causes the common uverbs\nvalidation code to emit an error message, uverbs_get_handler_fn()\ndereferences the uninitialized method_elm pointer.\n\nInitialize method_elm explicitly for legacy bundles and make\nuverbs_get_handler_fn() return NULL when no ioctl method is present. The\nlegacy dispatcher continues to use its local write method, while the ioctl\npath continues to use the registered ioctl handler.",
"id": "GHSA-6frh-mf5h-mgw9",
"modified": "2026-09-11T21:31:29Z",
"published": "2026-09-11T21:31:29Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89505"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/60a42d510113f46de47e86a84bf5758597644487"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/edae84e5461749ed9adf9fcf5c6e075381040ac3"
}
],
"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.