# CVE-2026-68418: RDMA/irdma: Prevent user-triggered null deref on QP create

> A local attacker can trigger a null pointer dereference in the Linux kernel RDMA driver, causing a system crash.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-95085, BELL-CVE-2026-68418, DEBIAN-CVE-2026-68418, GHSA-pfxp-3rpf-8hx8, UBUNTU-CVE-2026-68418

## What is CVE-2026-68418?

CVE-2026-68418 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

While there was a check for iwqp->iwpbl != NULL, this check
would only occur if req.user_wqe_bufs was non-zero. 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.

## Which versions are affected by CVE-2026-68418?


## How do I fix CVE-2026-68418?

Apply the vendor's patch.

## Is CVE-2026-68418 being exploited?

There is no known exploitation of CVE-2026-68418 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68418 and fix it if it is affected.

What it is: CVE-2026-68418 is a vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68418 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68418/ (Markdown: https://insights.sbomify.com/CVE-2026-68418/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68418
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68418
- OSV: https://osv.dev/vulnerability/CVE-2026-68418

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68418/
Summaries are generated and may contain mistakes; the official description above is the record.