{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80790 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2026-80790 is a vulnerability in Linux, published on 4 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-80790 and fix it if it is affected.\n\nWhat it is: CVE-2026-80790 is a vulnerability in Linux, published on 4 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-80790 in the wild and no public exploit code.\n\nAffected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-80790/ (Markdown: https://insights.sbomify.com/CVE-2026-80790/index.md)","id":"CVE-2026-80790","markdown":"https://insights.sbomify.com/CVE-2026-80790/index.md","name":"CVE-2026-80790","record":{"aliases":["AZL-99585","BELL-CVE-2026-80790","DEBIAN-CVE-2026-80790","GHSA-8g5c-jgpx-6xcv","UBUNTU-CVE-2026-80790"],"analysis":null,"analysis_generated_by":null,"assigner":"Linux","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"In the Linux kernel, the following vulnerability has been resolved:\n\nnvmet-fc: fix invalid free in LS IOD error path\n\nnvmet_fc_alloc_ls_iodlist() advances iod while initializing the LS IOD\narray. If an rqstbuf allocation or response buffer DMA mapping fails,\nthe unwind loop decrements iod past the start of the array. The final\nkfree(iod) therefore frees an address before the allocated object.\n\nThis can be reproduced with nvme-fcloop and failslab by setting\nfail-nth to 6 before creating a target port. KASAN reports:\n\n  BUG: KASAN: invalid-free in nvmet_fc_register_targetport\n  Free of addr ffff88816cf8ff48 by task nvmet_fail_nth/9552\n\nFree the original allocation base stored in tgtport-\u003eiod instead. With\nthis fix applied, the same sysfs write with fail-nth=6 returns -ENOMEM\nwithout any KASAN report.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"nvmet-fc: fix invalid free in LS IOD error path","id":"CVE-2026-80790","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":9,"next":{"headline":"nvmet-auth: zero the AUTH_RECEIVE response buffer","id":"CVE-2026-80791"},"packages":[],"prev":{"headline":"nvmet-tcp: bound SGL data length before allocating command buffers","id":"CVE-2026-80789"},"products":["Linux"],"published":"2026-09-04","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Linux"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-80790/"}