CVE-2026-80790 json
nvmet-fc: fix invalid free in LS IOD error path
published 2026-09-04 2 mo ago modified 2026-10-19 21 d ago also EUVD-2026-71433
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 9%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Linux Linux 5.10.267, 5.15.218, 6.1.185, 6.6.154, 6.12.106, 6.18.47, 7.1.11, 7.2.1, 7.3
- linux Debian 12 6.1.187-1
- linux Debian 13 6.12.107-1
- linux Debian 14 7.1.12-1
- linux-6.12 Debian 12 6.12.107-1~deb12u1
debian advisories DEBIAN-CVE-2026-80790
- linux Ubuntu 22.04 LTS 5.15.0-202.212
- linux Ubuntu 26.04 LTS 7.0.0-42.42
- linux-aws Ubuntu 22.04 LTS 5.15.0-1119.126
- linux-aws Ubuntu 26.04 LTS 7.0.0-1016.17
- linux-gcp Ubuntu 22.04 LTS 5.15.0-1120.130
- linux-gcp Ubuntu 26.04 LTS 7.0.0-1016.18
- linux-gke Ubuntu 22.04 LTS 5.15.0-1115.121
- linux-ibm Ubuntu 22.04 LTS 5.15.0-1113.117
ubuntu advisories UBUNTU-CVE-2026-80790
Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0
- kernel-source openSUSE Tumbleweed 7.2.5-1.1
opensuse advisories openSUSE-SU-2026:11773-1
- git.kernel.org/stable/c/b189c6e408896ccc23d2e76d7738847cdebf1532 commit
- git.kernel.org/stable/c/449e9c4f8db84ad9d9bb288029b230bcf590faa2 commit
- git.kernel.org/stable/c/1a8f007faefe8c226ec65896589f8d59b0a8d5a5 commit
- git.kernel.org/stable/c/d094582cce9c08516d714e7436a8f3b9211dda90 commit
- git.kernel.org/stable/c/371fb1bf902adaa59be32bd7e904a5317e604fd0 commit
- git.kernel.org/stable/c/8bce9cd08aae4283badf8ddc11fbb6f57b75a81e commit
- git.kernel.org/stable/c/bb9489f0dce58da730d3479588d6710d7a2c1b45 commit
- git.kernel.org/stable/c/94334ea92f4d7535f66f86e33681efa94827eddc commit
- git.kernel.org/stable/c/ba98d6796d12258e837ece065d2ecb59d76ce4ff commit
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-80790 updated cvss 4.7
kernel: nvmet-fc: fix invalid free in LS IOD error path
-
Red Hat Enterprise Linux 7 perf, kernel, bpftool, kernel-rt, python-perf, kernel-kdump, +8 more Red Hat Enterprise Linux 8 perf, kernel, bpftool, kernel-rt, kernel-core, kernel-tools, +29 more Red Hat Enterprise Linux 9 rv, perf, rtla, kernel, bpftool, libperf, +83 more Red Hat Enterprise Linux 10 kernel Red Hat OpenShift Container Platform 4 openshift/ose-rhel-coreos-8, openshift/ose-rhel-coreos-9 Red Hat OpenShift Container Platform 5 openshift/ose-rhel-coreos-9affected: workaround, no fix available “Fix deferred”
-
Red Hat Enterprise Linux 6 perf, kernel, python-perf, kernel-kdump, kernel-firmware, kernel-bootwrapper, +1 morenot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
0.19% chance of exploitation in the next 30 days, higher than 9% of all scored CVEs (FIRST EPSS, 2026-11-08).
Affected products
- Linux Linux
Classification
- Technology feeds
References
- git.kernel.org /stable/c/b189c6e408896ccc23d2e76d7738847cdebf1532
- git.kernel.org /stable/c/449e9c4f8db84ad9d9bb288029b230bcf590faa2
- git.kernel.org /stable/c/1a8f007faefe8c226ec65896589f8d59b0a8d5a5
- git.kernel.org /stable/c/d094582cce9c08516d714e7436a8f3b9211dda90
- git.kernel.org /stable/c/371fb1bf902adaa59be32bd7e904a5317e604fd0
- git.kernel.org /stable/c/8bce9cd08aae4283badf8ddc11fbb6f57b75a81e
- git.kernel.org /stable/c/bb9489f0dce58da730d3479588d6710d7a2c1b45
- git.kernel.org /stable/c/94334ea92f4d7535f66f86e33681efa94827eddc
- git.kernel.org /stable/c/ba98d6796d12258e837ece065d2ecb59d76ce4ff
Sources
- CVE List CVE-2026-80790
- NVD CVE-2026-80790
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.