CVE-2026-80790

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

N/A
Published: September 4, 2026 at 03:13 PM UTC
Updated: October 19, 2026 at 09:17 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

4.10c53432030d86429dc9fe5adc3d68cb9d1343b0b2
Vendor states this is fixed in 1a8f007faefe8c226ec65896589f8d59b0a8d5a5 (fixed)
Vendor states this is fixed in 371fb1bf902adaa59be32bd7e904a5317e604fd0 (fixed)
Vendor states this is fixed in 449e9c4f8db84ad9d9bb288029b230bcf590faa2 (fixed)
Vendor states this is fixed in 8bce9cd08aae4283badf8ddc11fbb6f57b75a81e (fixed)
Vendor states this is fixed in 94334ea92f4d7535f66f86e33681efa94827eddc (fixed)
Vendor states this is fixed in b189c6e408896ccc23d2e76d7738847cdebf1532 (fixed)
Vendor states this is fixed in ba98d6796d12258e837ece065d2ecb59d76ce4ff (fixed)
Vendor states this is fixed in bb9489f0dce58da730d3479588d6710d7a2c1b45 (fixed)
Vendor states this is fixed in d094582cce9c08516d714e7436a8f3b9211dda90 (fixed)
Vendor states this is fixed in 4.10 (unaffected)
Vendor states this is fixed in 5.10.267 (unaffected)
Vendor states this is fixed in 5.15.218 (unaffected)
Vendor states this is fixed in 6.1.185 (unaffected)
Vendor states this is fixed in 6.12.106 (unaffected)
Vendor states this is fixed in 6.18.47 (unaffected)
Vendor states this is fixed in 6.6.154 (unaffected)
Vendor states this is fixed in 7.1.11 (unaffected)
Vendor states this is fixed in 7.2.1 (unaffected)
Vendor states this is fixed in 7.3 (unaffected)
Vendor states this is fixed in 7.3-rc1 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card