FKIE_CVE-2026-89509
Vulnerability from fkie_nvd - Published: 2026-09-11 20:19 - Updated: 2026-09-11 20:19
Severity
Summary
In 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.
References
Impacted products
| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"defaultStatus": "unaffected",
"product": "Linux",
"programFiles": [
"drivers/infiniband/hw/ionic/ionic_hw_stats.c",
"drivers/infiniband/hw/ionic/ionic_ibdev.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"lessThan": "c98197ee3cd28288da13dc9881bb9e74daa7cbbc",
"status": "affected",
"version": "ea4c399642b85dc30f44d90ee805c6a18fa03062",
"versionType": "git"
},
{
"lessThan": "08b8630b557828aedb1d9ef0a6e2ec421f334ee2",
"status": "affected",
"version": "ea4c399642b85dc30f44d90ee805c6a18fa03062",
"versionType": "git"
},
{
"lessThan": "cf3ebd89e754015625fee90aa938f6bc79a2c974",
"status": "affected",
"version": "ea4c399642b85dc30f44d90ee805c6a18fa03062",
"versionType": "git"
}
]
},
{
"defaultStatus": "affected",
"product": "Linux",
"programFiles": [
"drivers/infiniband/hw/ionic/ionic_hw_stats.c",
"drivers/infiniband/hw/ionic/ionic_ibdev.h"
],
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"vendor": "Linux",
"versions": [
{
"status": "affected",
"version": "6.18"
},
{
"lessThan": "6.18",
"status": "unaffected",
"version": "0",
"versionType": "semver"
},
{
"lessThanOrEqual": "6.18.*",
"status": "unaffected",
"version": "6.18.51",
"versionType": "semver"
},
{
"lessThanOrEqual": "7.2.*",
"status": "unaffected",
"version": "7.2.4",
"versionType": "semver"
},
{
"lessThanOrEqual": "*",
"status": "unaffected",
"version": "7.3-rc1",
"versionType": "original_commit_for_fix"
}
]
}
],
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "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": "CVE-2026-89509",
"lastModified": "2026-09-11T20:19:33.273",
"metrics": {},
"published": "2026-09-11T20:19:33.273",
"references": [
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/08b8630b557828aedb1d9ef0a6e2ec421f334ee2"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/c98197ee3cd28288da13dc9881bb9e74daa7cbbc"
},
{
"source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"url": "https://git.kernel.org/stable/c/cf3ebd89e754015625fee90aa938f6bc79a2c974"
}
],
"sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
"vulnStatus": "Received"
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
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.
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
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.
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.
Loading…
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.
Loading…