Menu

Star on GitHub · 3.2k

CVE-2025-38658

8.8 · HIGH

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 fail…

Published Aug 22, 2025CWE-908EPSS 0.20%

Overview

CVE-2025-38658 is a high-severity vulnerability. It was published on August 22, 2025 and has a CVSS 3.1 base score of 8.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

Technical description

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

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently asked questions

What is CVE-2025-38658?

CVE-2025-38658 is a high-severity vulnerability. It was published on August 22, 2025 and has a CVSS 3.1 base score of 8.8 (HIGH).

How severe is CVE-2025-38658?

This vulnerability has a CVSS 3.1 base score of 8.8, rated HIGH. It requires local or adjacent network access to exploit. No authentication or special privileges are required for exploitation.

How do I fix or remediate CVE-2025-38658?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2025-38658?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-38658 is actually reachable in your own applications and APIs, then verifies each finding before reporting it. That tells you if the weakness is a real, exploitable risk in your environment or a false positive you can safely deprioritize.

Related HIGH CVEs from 2025

View all