In the Linux kernel, the following vulnerability has been resolved: RDMA/ionic: Embed counter driver data in rdma_counter allocation Commit… (CVE-2026-89509)
A vulnerability in the Linux kernel's RDMA ionic driver was resolved by embedding counter driver data properly in the rdma_counter allocation. The issue was caused by the ionic driver not adapting to a required change in the RDMA core, leading to a NULL pointer dereference due to zero-byte allocation. The fix involved consolidating the ionic_counter structure, replacing the ID allocation method, and adding necessary initialization declarations.
AI Analysis
Technical Summary
The Linux kernel RDMA ionic driver did not implement the required adaptation introduced by commit 7e53b31acc7f, which mandates that drivers embedding struct rdma_counter register its size and provide a counter_init callback. The ionic driver failed to set size_rdma_counter, causing rdma_zalloc_drv_obj() to allocate zero bytes and resulting in a NULL pointer dereference in alloc_and_bind(). The vulnerability was fixed by consolidating ionic_counter into ionic_rdma_counter embedding struct rdma_counter, replacing the xarray with a lightweight ID allocator, and adding the required counter_init and INIT_RDMA_OBJ_SIZE declarations.
Potential Impact
This vulnerability could cause a NULL pointer dereference in the Linux kernel RDMA ionic driver, potentially leading to kernel crashes or denial of service. No information about exploitation in the wild or further impact is provided.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source code by consolidating the ionic_counter structure and adding the required initialization declarations. Users should update to the fixed kernel version containing this patch. Patch status is not explicitly stated; check the vendor or Linux kernel advisory for the exact fixed version and update accordingly.
In the Linux kernel, the following vulnerability has been resolved: RDMA/ionic: Embed counter driver data in rdma_counter allocation Commit… (CVE-2026-89509)
Description
A vulnerability in the Linux kernel's RDMA ionic driver was resolved by embedding counter driver data properly in the rdma_counter allocation. The issue was caused by the ionic driver not adapting to a required change in the RDMA core, leading to a NULL pointer dereference due to zero-byte allocation. The fix involved consolidating the ionic_counter structure, replacing the ID allocation method, and adding necessary initialization declarations.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The Linux kernel RDMA ionic driver did not implement the required adaptation introduced by commit 7e53b31acc7f, which mandates that drivers embedding struct rdma_counter register its size and provide a counter_init callback. The ionic driver failed to set size_rdma_counter, causing rdma_zalloc_drv_obj() to allocate zero bytes and resulting in a NULL pointer dereference in alloc_and_bind(). The vulnerability was fixed by consolidating ionic_counter into ionic_rdma_counter embedding struct rdma_counter, replacing the xarray with a lightweight ID allocator, and adding the required counter_init and INIT_RDMA_OBJ_SIZE declarations.
Potential Impact
This vulnerability could cause a NULL pointer dereference in the Linux kernel RDMA ionic driver, potentially leading to kernel crashes or denial of service. No information about exploitation in the wild or further impact is provided.
Mitigation Recommendations
A fix has been implemented in the Linux kernel source code by consolidating the ionic_counter structure and adding the required initialization declarations. Users should update to the fixed kernel version containing this patch. Patch status is not explicitly stated; check the vendor or Linux kernel advisory for the exact fixed version and update accordingly.
Technical Details
- Gcve Source
- db.gcve.eu
- Osv Id
- GHSA-p644-p7x2-xc3f
- Osv Schema Version
- 1.4.0
- Aliases
- ["CVE-2026-89509"]
Threat ID: 6aa4a01455bf5e2cf5a866d0
Added to database: 09/12/2026, 00:43:00 UTC
Last enriched: 09/12/2026, 01:09:53 UTC
Last updated: 09/12/2026, 01:09:53 UTC
Views: 2
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.