CVE-2025-40001

UnknownEPSS 0.24%

Last modified

CVE-2025-40001 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.24% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.24%

14.5th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 20b09c2992fefbe78f8cede7b404fb143a413c52, < a6f68f219d4d4b92d7c781708d4afc4cc42961ec; >= 20b09c2992fefbe78f8cede7b404fb143a413c52, < aacd1777d4a795c387a20b9ca776e2c1225d05d7; >= 20b09c2992fefbe78f8cede7b404fb143a413c52, < 6ba7e73cafd155a5d3abf560d315f0bab2b9d89f; >= 20b09c2992fefbe78f8cede7b404fb143a413c52, < c2c35cb2a31844f84f21ab364b38b4309d756d42; >= 20b09c2992fefbe78f8cede7b404fb143a413c52, < 3c90f583d679c81a5a607a6ae0051251b6dee35b; >= 20b09c2992fefbe78f8cede7b404fb143a413c52, < 00d3af40b158ebf7c7db2b3bbb1598a54bf28127; >= 20b09c2992fefbe78f8cede7b404fb143a413c52, < feb946d2fc9dc754bf3d594d42cd228860ff8647; >= 20b09c2992fefbe78f8cede7b404fb143a413c52, < 60cd16a3b7439ccb699d0bf533799eeb894fd217
LinuxLinux2.6.31

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is 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 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.
How severe is CVE-2025-40001?
Severity scoring for CVE-2025-40001 is pending analysis. The EPSS model estimates a 0.24% probability of exploitation in the next 30 days.
How do I fix CVE-2025-40001?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2025

Are you affected by CVE-2025-40001?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST