# CVE-2025-40001: scsi: mvsas: Fix use-after-free bugs in mvs_work_queue

> A use-after-free vulnerability in the Linux kernel mvsas driver allows local attackers to cause denial of service or execute code during device detachment.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2025
- **Updated:** 11 May 2026
- **Also known as:** AZL-68585, BELL-CVE-2025-40001, DEBIAN-CVE-2025-40001, GHSA-q5hm-2p5x-hm8x, ROOT-OS-DEBIAN-11-CVE-2025-40001, ROOT-OS-DEBIAN-12-CVE-2025-40001, ROOT-OS-DEBIAN-13-CVE-2025-40001, ROOT-OS-UBUNTU-2204-CVE-2025-40001, ROOT-OS-UBUNTU-2404-CVE-2025-40001, UBUNTU-CVE-2025-40001

## What is CVE-2025-40001?

CVE-2025-40001 is an use after free vulnerability in Linux, published on 18 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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 before the mvs_info is deallocated.

This bug was found by static analysis.

## Which versions are affected by CVE-2025-40001?


## How do I fix CVE-2025-40001?

Apply the vendor's patch.

## Is CVE-2025-40001 being exploited?

There is no known exploitation of CVE-2025-40001 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40001 and fix it if it is affected.

What it is: CVE-2025-40001 is an use after free vulnerability in Linux, published on 18 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-40001 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-40001/ (Markdown: https://insights.sbomify.com/CVE-2025-40001/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-40001
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-40001
- OSV: https://osv.dev/vulnerability/CVE-2025-40001

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-40001/
Summaries are generated and may contain mistakes; the official description above is the record.