Medium [CVE-2026-68418] Prevent user-triggered null deref on QP create
This medium-severity Red Hat Linux advisory covers CVE-2026-68418 affecting Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
In the Linux kernel, the following vulnerability has been resolved: RDMA/irdma: Prevent user-triggered null deref on QP create Previously, the user QP creation path would only attempt to populate iwqp->iwpbl if the user-provided req.user_wqe_bufs field was non-zero.
The problem is that iwqp->iwpbl is unconditionally dereferenced later on in irdma_setup_virt_qp. The end result is that a user could send a zero user_wqe_bufs value and trigger a null ptr deref.
Fix this by unconditionally calling irdma_get_pbl and bailing if it fails, similar to the CQ and SRQ paths. A local user could exploit this vulnerability by providing a zero value for `user_wqe_bufs` during the creation of a Queue Pair (QP).
This action leads to a null pointer dereference, which can cause the system to crash, resulting in a Denial of Service (DoS). This issue affects systems using the Intel RDMA (irdma) driver.
A local user creating a queue pair with user_wqe_bufs set to zero can trigger a NULL pointer dereference because iwpbl is not allocated but is later dereferenced unconditionally. Systems without irdma/RDMA userspace access are not affected.
Red Hat severity: Low — CVSS 5.5 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H). Weakness: CWE-476.
Affected Red Hat products: Red Hat Enterprise Linux 10; Red Hat Enterprise Linux 8; Red Hat Enterprise Linux 9; Red Hat Enterprise Linux for NVIDIA 26.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Mitigation checklist
- To mitigate this issue, prevent the irdma module from loading. See https://access.redhat.com/solutions/41278 for instructions.
Official advisory · high-confidence parse· fetched 2 days ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.