GHSA-P644-P7X2-XC3F
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/ionic: Embed counter driver data in rdma_counter allocation
Commit 7e53b31acc7f ("RDMA/core: Create and destroy rdma_counter using rdma_zalloc_drv_obj()") requires drivers implementing counter ops to embed struct rdma_counter in a driver-specific struct, register its size via INIT_RDMA_OBJ_SIZE, and provide a counter_init callback.
The ionic driver was merged without this adaptation, causing a NULL pointer dereference in alloc_and_bind() since rdma_zalloc_drv_obj() allocates zero bytes when size_rdma_counter is unset.
Consolidate struct ionic_counter into a new struct ionic_rdma_counter that embeds struct rdma_counter, replace the xarray with a lightweight ida for ID allocation, and add the required counter_init and INIT_RDMA_OBJ_SIZE declarations.
{
"affected": [],
"aliases": [
"CVE-2026-89509"
],
"database_specific": {
"cwe_ids": [],
"github_reviewed": false,
"github_reviewed_at": null,
"nvd_published_at": "2026-09-11T20:19:33Z",
"severity": null
},
"details": "In the Linux kernel, the following vulnerability has been resolved:\n\nRDMA/ionic: Embed counter driver data in rdma_counter allocation\n\nCommit 7e53b31acc7f (\"RDMA/core: Create and destroy rdma_counter using\nrdma_zalloc_drv_obj()\") requires drivers implementing counter ops to\nembed struct rdma_counter in a driver-specific struct, register its size\nvia INIT_RDMA_OBJ_SIZE, and provide a counter_init callback.\n\nThe ionic driver was merged without this adaptation, causing a NULL\npointer dereference in alloc_and_bind() since rdma_zalloc_drv_obj()\nallocates zero bytes when size_rdma_counter is unset.\n\nConsolidate struct ionic_counter into a new struct ionic_rdma_counter\nthat embeds struct rdma_counter, replace the xarray with a lightweight\nida for ID allocation, and add the required counter_init and\nINIT_RDMA_OBJ_SIZE declarations.",
"id": "GHSA-p644-p7x2-xc3f",
"modified": "2026-09-11T21:31:30Z",
"published": "2026-09-11T21:31:30Z",
"references": [
{
"type": "ADVISORY",
"url": "https://nvd.nist.gov/vuln/detail/CVE-2026-89509"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/08b8630b557828aedb1d9ef0a6e2ec421f334ee2"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/c98197ee3cd28288da13dc9881bb9e74daa7cbbc"
},
{
"type": "WEB",
"url": "https://git.kernel.org/stable/c/cf3ebd89e754015625fee90aa938f6bc79a2c974"
}
],
"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.