# CVE-2025-68371: scsi: smartpqi: Fix device resources accessed after device removal

> A race condition in the smartpqi SCSI driver allows use-after-free during device removal, potentially leading to code execution or denial of service.

- **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:** 24 Dec 2025
- **Updated:** 15 Oct 2026
- **Also known as:** AZL-73054, BELL-CVE-2025-68371, DEBIAN-CVE-2025-68371, GHSA-ch5r-r49p-5xqv, ROOT-OS-DEBIAN-12-CVE-2025-68371, ROOT-OS-UBUNTU-2204-CVE-2025-68371, ROOT-OS-UBUNTU-2404-CVE-2025-68371, UBUNTU-CVE-2025-68371

## What is CVE-2025-68371?

CVE-2025-68371 is an use after free vulnerability in Linux, published on 24 Dec 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: 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.

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


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

Apply the vendor's patch.

## Is CVE-2025-68371 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68371 is an use after free vulnerability in Linux, published on 24 Dec 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-68371 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-68371/ (Markdown: https://insights.sbomify.com/CVE-2025-68371/index.md)
```

## Sources

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

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