# CVE-2026-93103: RDMA/hfi1: Preserve unit 0 on allocation failure

> A flaw in the Linux kernel hfi1 driver allows an attacker to cause a denial of service by triggering an allocation failure that corrupts the device unit table.

- **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-102099, BELL-CVE-2026-93103, DEBIAN-CVE-2026-93103, GHSA-jjcw-q5gq-x45h, UBUNTU-CVE-2026-93103

## What is CVE-2026-93103?

CVE-2026-93103 is a 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: Preserve unit 0 on allocation failure

hfi1_free_devdata() assumes that the device was inserted into the unit
table and unconditionally erases dd->unit. If xa_alloc_irq() fails, the
zero-initialized unit remains zero, so full cleanup can remove an
unrelated device from index 0.

Release only the rdmavt allocation and return immediately while the unit
table has not acquired the device.

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


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

Apply the vendor's patch.

## Is CVE-2026-93103 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93103 is a 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-93103 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-93103/ (Markdown: https://insights.sbomify.com/CVE-2026-93103/index.md)
```

## Sources

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

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