Strix
26.1K

CVE-2025-68371

UnknownEPSS 0.16%

Last modified

CVE-2025-68371 is a vulnerability of currently unknown severity. In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix device resources accessed after device removal Correct possible race conditions during device removal. Previously, a scheduled work item to reset a LUN could still execute after the device was removed, leading to use-after-free and other resource access issues. This race condition occurs because the abort handler may schedule a LUN reset concurrently with device removal via sdev_destroy(), leading to use-after-free and improper access to freed resources. - Check in the device reset handler if the device is still present in the controller's SCSI device list before running; if not, the reset is skipped. - Cancel any pending TMF work that has not started in sdev_destroy(). - Ensure device freeing in sdev_destroy() is done while holding the LUN reset mutex to avoid races with ongoing resets.. EPSS estimates a 0.16% chance of exploitation in the next 30 days.

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix device resources accessed after device removal Correct possible race conditions during device removal. Previously, a scheduled work item to reset a LUN could still execute after the device was removed, leading to use-after-free and other resource access issues. This race condition occurs because the abort handler may schedule a LUN reset concurrently with device removal via sdev_destroy(), leading to use-after-free and improper access to freed resources. - Check in the device reset handler if the device is still present in the controller's SCSI device list before running; if not, the reset is skipped. - Cancel any pending TMF work that has not started in sdev_destroy(). - Ensure device freeing in sdev_destroy() is done while holding the LUN reset mutex to avoid races with ongoing resets.

Metrics

EPSS Probability
0.16%

5.7th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

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

VendorProductVersions
LinuxLinux>= 2d80f4054f7f901b8ad97358a9069616ac8524c7, < 7dfa5a5516ec3c6b9b6c22ee18f0eb2df3f38ef2; >= 2d80f4054f7f901b8ad97358a9069616ac8524c7, < 6d2390653d82cad0e1ba2676e536dd99678f6ef1; >= 2d80f4054f7f901b8ad97358a9069616ac8524c7, < eccc02ba1747501d92bb2049e3ce378ba372f641; >= 2d80f4054f7f901b8ad97358a9069616ac8524c7, < 4e1acf1b6dd6dd0495bda139daafd7a403ae2dc1; >= 2d80f4054f7f901b8ad97358a9069616ac8524c7, < 1a5c5a2f88e839af5320216a02ffb075b668596a; >= 2d80f4054f7f901b8ad97358a9069616ac8524c7, < b518e86d1a70a88f6592a7c396cf1b93493d1aab
LinuxLinux6.0

References

Timeline

Published
Last Modified
Status
Deferred

Frequently Asked Questions

What is CVE-2025-68371?
In the Linux kernel, the following vulnerability has been resolved: scsi: smartpqi: Fix device resources accessed after device removal Correct possible race conditions during device removal. Previously, a scheduled work item to reset a LUN could still execute after the device was removed, leading to use-after-free and other resource access issues. This race condition occurs because the abort handler may schedule a LUN reset concurrently with device removal via sdev_destroy(), leading to use-after-free and improper access to freed resources. - Check in the device reset handler if the device is still present in the controller's SCSI device list before running; if not, the reset is skipped. - Cancel any pending TMF work that has not started in sdev_destroy(). - Ensure device freeing in sdev_destroy() is done while holding the LUN reset mutex to avoid races with ongoing resets.
How severe is CVE-2025-68371?
Severity scoring for CVE-2025-68371 is pending analysis. The EPSS model estimates a 0.16% probability of exploitation in the next 30 days.
How do I fix CVE-2025-68371?
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

View all 2025CVEs →

Are you affected by CVE-2025-68371?

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

Scan your code now

Source: NVD / NIST