# CVE-2025-68745: scsi: qla2xxx: Clear cmds after chip reset

> A race condition in the qla2xxx SCSI driver causes a kernel crash during chip reset, leading to denial of service.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Dec 2025
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-73087, BELL-CVE-2025-68745, DEBIAN-CVE-2025-68745, GHSA-vc2w-h9rc-mpxx, ROOT-OS-DEBIAN-11-CVE-2025-68745, ROOT-OS-DEBIAN-12-CVE-2025-68745, ROOT-OS-DEBIAN-13-CVE-2025-68745, ROOT-OS-UBUNTU-2204-CVE-2025-68745, ROOT-OS-UBUNTU-2404-CVE-2025-68745, UBUNTU-CVE-2025-68745

## What is CVE-2025-68745?

CVE-2025-68745 is a critical vulnerability in Linux, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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

scsi: qla2xxx: Clear cmds after chip reset

Commit aefed3e5548f ("scsi: qla2xxx: target: Fix offline port handling
and host reset handling") caused two problems:

1. Commands sent to FW, after chip reset got stuck and never freed as FW
   is not going to respond to them anymore.

2. BUG_ON(cmd->sg_mapped) in qlt_free_cmd().  Commit 26f9ce53817a
   ("scsi: qla2xxx: Fix missed DMA unmap for aborted commands")
   attempted to fix this, but introduced another bug under different
   circumstances when two different CPUs were racing to call
   qlt_unmap_sg() at the same time: BUG_ON(!valid_dma_direction(dir)) in
   dma_unmap_sg_attrs().

So revert "scsi: qla2xxx: Fix missed DMA unmap for aborted commands" and
partially revert "scsi: qla2xxx: target: Fix offline port handling and
host reset handling" at __qla2x00_abort_all_cmds.

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


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

Apply the vendor's patch.

## Is CVE-2025-68745 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-68745 is a critical vulnerability in Linux, published on 24 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68745 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-68745/ (Markdown: https://insights.sbomify.com/CVE-2025-68745/index.md)
```

## Sources

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

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