Menu

Star on GitHub · 3.2k

CVE-2025-40001

In the Linux kernel, the following vulnerability has been resolved: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue During the detaching of Marvell's SAS/SATA controller, the original code…

Published Oct 18, 2025EPSS 0.26%

Overview

CVE-2025-40001 is a known-severity vulnerability. It was published on October 18, 2025.

Technical description

In the Linux kernel, the following vulnerability has been resolved:

scsi: mvsas: Fix use-after-free bugs in mvs_work_queue

During the detaching of Marvell's SAS/SATA controller, the original code

calls cancel_delayed_work() in mvs_free() to cancel the delayed work

item mwq->work_q. However, if mwq->work_q is already running, the

cancel_delayed_work() may fail to cancel it. This can lead to

use-after-free scenarios where mvs_free() frees the mvs_info while

mvs_work_queue() is still executing and attempts to access the

already-freed mvs_info.

A typical race condition is illustrated below:

CPU 0 (remove) | CPU 1 (delayed work callback)

mvs_pci_remove() |

mvs_free() | mvs_work_queue()

cancel_delayed_work() |

kfree(mvi) |

| mvi-> // UAF

Replace cancel_delayed_work() with cancel_delayed_work_sync() to ensure

that the delayed work item is properly canceled and any executing

delayed work item completes befor

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-40001?

CVE-2025-40001 is a known-severity vulnerability. It was published on October 18, 2025.

How severe is CVE-2025-40001?

CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.

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

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-40001?

CyberStrike is an open-source, AI-augmented pentesting engine. Rather than flag a version number, it tests whether an issue like CVE-2025-40001 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.