Impact
The vulnerability arises because the ionic RDMA driver fails to register the size of its embedded rdma_counter structure during module creation. As a result, rdma_zalloc_drv_obj() allocates zero bytes for the counter, and a subsequent NULL pointer dereference in alloc_and_bind() triggers a kernel panic. The effect is a system‑wide crash. The weakness is a NULL pointer dereference (CWE‑476).
Affected Systems
All Linux kernel releases that ship the ionic RDMA driver without the commit that registers INIT_RDMA_OBJ_SIZE are affected. The description implicitly indicates that any system with that version of the driver and the driver loaded is at risk; this is inferred from the commit context and the mention that the ionic driver was merged without the necessary adaptation. If RDMA is disabled or the driver is not loaded, the vulnerability does not manifest.
Risk and Exploitability
The CVSS v3.1 score of 4.1 classifies the flaw as low severity. The EPSS score of <1% suggests a very low likelihood of real‑world exploitation. The vulnerability is not listed in CISA KEV. Exploitation would require the ability to load or already have the faulty ionic driver active, implying root or privileged module load rights. If achieved, the attacker would cause an immediate kernel crash, resulting in a denial of service.
OpenCVE Enrichment