RDMA/ionic: Embed counter driver data in rdma_counter allocation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.18.51, 7.2.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
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.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From ea4c399642b85dc30f44d90ee805c6a18fa03062 · fixed in c98197ee3cd28288da13dc9881bb9e74daa7cbbc; From ea4c399642b85dc30f44d90ee805c6a18fa03062 · fixed in 08b8630b557828aedb1d9ef0a6e2ec421f334ee2; From ea4c399642b85dc30f44d90ee805c6a18fa03062 · fixed in cf3ebd89e754015625fee90aa938f6bc79a2c974
- Linux Linux
6.18
- KernelLinux
From 6.18.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.4