# CVE-2026-98355: RDMA/rtrs: guard against null kobj name

> A null pointer dereference in the Linux kernel RDMA client allows local attackers to cause a denial of service via error handling paths.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-106209, BELL-CVE-2026-98355, DEBIAN-CVE-2026-98355, GHSA-w8vc-67qx-3qw3, UBUNTU-CVE-2026-98355

## What is CVE-2026-98355?

CVE-2026-98355 is a vulnerability in Linux, published on 6 Oct 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/rtrs: guard against null kobj name

In the client, if `init_path()` errors, the callee tries to clean up
with `rtrs_clt_close_conns()`. However, this can lead to calling the
event tracing code with `clt_path->kobj->name` being `NULL` and thus
causing a null pointer dereference when trying to copy from it.

This just adds a guard to check that the name is not `NULL` before
copying from it. The server appears to have a similar pattern.

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


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

Apply the vendor's patch.

## Is CVE-2026-98355 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98355 is a vulnerability in Linux, published on 6 Oct 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-98355 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-98355/ (Markdown: https://insights.sbomify.com/CVE-2026-98355/index.md)
```

## Sources

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

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