CVE-2025-38658

published 22 Aug 2025 · updated 5 Aug 2026

nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails

8.8HighCVSS 8.8EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 746d0ac5a07d5da952ef258dd4d75f0b26c96476 and Kernel a535c0b10060bc8c174a7964b0f98064ee0c4774.

In the Linux kernel, the following vulnerability has been resolved: nvmet: pci-epf: Do not complete commands twice if nvmet_req_init() fails Have nvmet_req_init() and req->execute() complete failed commands. Description of the problem: nvmet_req_init() calls __nvmet_req_complete() internally upon failure, e.g., unsupported opcode, which calls the "queue_response" callback, this results in nvmet_pci_epf_queue_response() being called, which will call nvmet_pci_epf_complete_iod() if data_len is 0 or if dma_dir is different from DMA_TO_DEVICE. This results in a double completion as nvmet_pci_epf_exec_iod_work() also calls nvmet_pci_epf_complete_iod() when nvmet_req_init() fails. Steps to reproduce: On the host send a command with an unsupported opcode with nvme-cli, For example the admin command "security receive" $ sudo nvme security-recv /dev/nvme0n1 -n1 -x4096 This triggers a double completion as nvmet_req_init() fails and nvmet_pci_epf_queue_response() is called, here iod->dma_dir is still in the default state of "DMA_NONE" as set by default in nvmet_pci_epf_alloc_iod(), so nvmet_pci_epf_complete_iod() is called. Because nvmet_req_init() failed nvmet_pci_epf_complete_iod() is also called in nvmet_pci_epf_exec_iod_work() leading to a double completion. This not only sends two completions to the host but also corrupts the state of the PCI NVMe target leading to kernel oops. This patch lets nvmet_req_init() and req->execute() complete all failed commands, and removes the double completion case in nvmet_pci_epf_exec_iod_work() therefore fixing the edge cases where double completions occurred.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=6.14, >=0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 <746d0ac5a07d5da952ef258dd4d75f0b26c96476, >=0faa0fe6f90ea59b10d1b0f15ce0eb0c18eff186 <a535c0b10060bc8c174a7964b0f98064ee0c4774746d0ac5a07d5da952ef258dd4d75f0b26c96476, a535c0b10060bc8c174a7964b0f98064ee0c4774

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-38658 severity on Zeptric[![CVE-2025-38658](https://zeptric.io/badge/cve/CVE-2025-38658.svg)](https://zeptric.io/cve/CVE-2025-38658)