# CVE-2026-93102: RDMA/hfi1: Free RX data on late probe failure

> A memory leak in the Linux kernel RDMA hfi1 driver allows local attackers to cause denial of service by triggering a late probe failure.

- **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:** 17 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-102297, BELL-CVE-2026-93102, DEBIAN-CVE-2026-93102, GHSA-pccp-57xf-cm47, UBUNTU-CVE-2026-93102

## What is CVE-2026-93102?

CVE-2026-93102 is a memory corruption vulnerability in Linux, published on 17 Sep 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/hfi1: Free RX data on late probe failure

hfi1_init_dd() allocates the shared AIP/VNIC RX support before returning.
If hfi1_init() or hfi1_register_ib_device() later fails, init_one() tears
down the device data without calling hfi1_free_rx(). This leaks netdev_rx
and its dummy netdev.

Free the RX support after IB unregistration and before postinit_cleanup(),
as done on normal device removal.

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


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

Apply the vendor's patch.

## Is CVE-2026-93102 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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