# CVE-2026-80790: nvmet-fc: fix invalid free in LS IOD error path


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 4 Sep 2026
- **Updated:** 19 Oct 2026
- **Also known as:** AZL-99585, BELL-CVE-2026-80790, DEBIAN-CVE-2026-80790, GHSA-8g5c-jgpx-6xcv, UBUNTU-CVE-2026-80790

## What is CVE-2026-80790?

CVE-2026-80790 is a vulnerability in Linux, published on 4 Sep 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

nvmet-fc: fix invalid free in LS IOD error path

nvmet_fc_alloc_ls_iodlist() advances iod while initializing the LS IOD
array. If an rqstbuf allocation or response buffer DMA mapping fails,
the unwind loop decrements iod past the start of the array. The final
kfree(iod) therefore frees an address before the allocated object.

This can be reproduced with nvme-fcloop and failslab by setting
fail-nth to 6 before creating a target port. KASAN reports:

  BUG: KASAN: invalid-free in nvmet_fc_register_targetport
  Free of addr ffff88816cf8ff48 by task nvmet_fail_nth/9552

Free the original allocation base stored in tgtport->iod instead. With
this fix applied, the same sysfs write with fail-nth=6 returns -ENOMEM
without any KASAN report.

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


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

Upgrade to a fixed version.

## Is CVE-2026-80790 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-80790 is a vulnerability in Linux, published on 4 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-80790 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-80790/ (Markdown: https://insights.sbomify.com/CVE-2026-80790/index.md)
```

## Sources

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

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