CVE-2026-80790
nvmet-fc: fix invalid free in LS IOD error path
Reported by linux · Published September 4, 2026
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.
EPSS 0.19% · 9.2th percentile
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| Linux | Linux | d094582cce9c08516d714e7436a8f3b9211dda90, bb9489f0dce58da730d3479588d6710d7a2c1b45, ba98d6796d12258e837ece065d2ecb59d76ce4ff, b189c6e408896ccc23d2e76d7738847cdebf1532, 94334ea92f4d7535f66f86e33681efa94827eddc, 8bce9cd08aae4283badf8ddc11fbb6f57b75a81e, 449e9c4f8db84ad9d9bb288029b230bcf590faa2, 371fb1bf902adaa59be32bd7e904a5317e604fd0, 1a8f007faefe8c226ec65896589f8d59b0a8d5a5 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | c53432030d86429dc9fe5adc3d68cb9d1343b0b2, c53432030d86429dc9fe5adc3d68cb9d1343b0b2, c53432030d86429dc9fe5adc3d68cb9d1343b0b2 |
| Linux | Linux | 4.10, 0, 5.10.267 |
| Linux | Linux | 7.3, 0, 5.10.267 |
| linux | linux_kernel | 4.10, 4.10, 4.10 |
Timeline
- Sep 4, 2026 Coalition ESS Score
- Sep 4, 2026 CVE Published
- Sep 5, 2026 EPSS Score (14 in total, the first dated here)
- Oct 19, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln CVE-2026-80790
vulnetix vdb fixes CVE-2026-80790
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/CVE-2026-80790/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart