{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-80787 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2026-80787 is an use after free vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-80787 and fix it if it is affected.\n\nWhat it is: CVE-2026-80787 is an use after free vulnerability in Linux, published on 4 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-80787 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-80787/ (Markdown: https://insights.sbomify.com/CVE-2026-80787/index.md)","id":"CVE-2026-80787","markdown":"https://insights.sbomify.com/CVE-2026-80787/index.md","name":"CVE-2026-80787","record":{"aliases":["BELL-CVE-2026-80787","DEBIAN-CVE-2026-80787","GHSA-xprc-p39c-6w43","UBUNTU-CVE-2026-80787"],"analysis":{"component_type":"kernel","fix_type":"patch","impacts":["denial_of_service","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Linux kernel","requires_auth":"none","summary":"A use-after-free vulnerability in the Linux kernel's NVMe PCI endpoint function driver allows local attackers to cause a denial of service or potentially execute code.","user_interaction":"not_required","vuln_class":"use_after_free"},"analysis_generated_by":"qwen3.8-flash-next","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: pci-epf: fix use-after-free in nvmet_pci_epf_exec_iod_work()\n\nnvmet_pci_epf_exec_iod_work() submits an I/O command with req-\u003eexecute()\nand then waits for the command to complete and transfers the data back\nto the host. This wait is not needed for commands that do not transfer\ndata from the device to the host. To decide whether that wait is needed,\nit reads iod-\u003edata_len and iod-\u003edma_dir after calling req-\u003eexecute().\n\nHowever, once req-\u003eexecute() is called, the command may complete\nasynchronously on another CPU. For commands that do not require a\ndevice-to-host data transfer, nvmet_pci_epf_queue_response() calls\nnvmet_pci_epf_complete_iod() directly, which can free the iod before it\nreads iod-\u003edata_len and iod-\u003edma_dir, resulting in the KFENCE use-after-\nfree:\n\n BUG: KFENCE: use-after-free read in nvmet_pci_epf_exec_iod_work+0x288/0x798 [nvmet_pci_epf]\n\n Use-after-free read at 0x00000000fdfa6d03 (in kfence-#63):\n  nvmet_pci_epf_exec_iod_work+0x288/0x798 [nvmet_pci_epf]\n  process_one_work+0x15c/0x4f0\n  worker_thread+0x18c/0x30c\n  kthread+0x130/0x140\n  ret_from_fork+0x10/0x20\n\n kfence-#63: 0x00000000e3de0e71-0x00000000c938ad62, size=712, cache=kmalloc-1k\n\n allocated by task 10 on cpu 0 at 73.995480s (0.005122s ago):\n  mempool_kmalloc+0x1c/0x28\n  mempool_alloc_noprof+0x40/0x9c\n  nvmet_pci_epf_poll_sqs_work+0xd4/0x344 [nvmet_pci_epf]\n  process_one_work+0x15c/0x4f0\n  worker_thread+0x18c/0x30c\n  kthread+0x130/0x140\n  ret_from_fork+0x10/0x20\n\n freed by task 131 on cpu 3 at 73.995521s (0.008385s ago):\n  mempool_kfree+0x10/0x20\n  mempool_free+0x44/0x64\n  nvmet_pci_epf_free_iod+0x88/0x98 [nvmet_pci_epf]\n  nvmet_pci_epf_cq_work+0xfc/0x280 [nvmet_pci_epf]\n  process_one_work+0x15c/0x4f0\n  worker_thread+0x18c/0x30c\n  kthread+0x130/0x140\n  ret_from_fork+0x10/0x20\n\nFix this by referring to iod-\u003edata_len and iod-\u003edma_dir before calling\nreq-\u003eexecute(). The remaining iod accesses such as iod-\u003estatus are only\nreached on the device-to-host read path. In this case,\nnvmet_pci_epf_queue_response() signals iod-\u003edone instead of freeing the\niod, so the iod stays valid.","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: pci-epf: fix use-after-free in nvmet_pci_epf_exec_iod_work()","id":"CVE-2026-80787","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"use_after_free","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"nvmet-tcp: Do not WARN on remotely-controlled oversized SGL allocations","id":"CVE-2026-80788"},"packages":[],"prev":{"headline":"fbdev: Wrap user-invoked calls to fb_set_var() in helper","id":"CVE-2026-80786"},"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":"A use-after-free vulnerability in the Linux kernel's NVMe PCI endpoint function driver allows local attackers to cause a denial of service or potentially execute code.","url":"https://insights.sbomify.com/CVE-2026-80787/"}