scsi: qla2xxx: Clear cmds after chip reset
Linux kernel qla2xxx SCSI driver, affected when a chip reset happens with commands outstanding to firmware. CVSS rates it critical (9.8). Fixed in stable kernels 6.6.160, 6.12.114 and 6.18.2 and later.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Fix
- Fixed in 4.10, 4.15, 4.20, 6.6.160, 6.12.114, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
The vulnerability affects the Linux kernel's SCSI driver for QLogic Fibre Channel host adapters (qla2xxx), specifically its target-mode handling after a chip reset. The flaw can leave commands sent to the adapter firmware stuck and unfreed, and can trigger kernel crashes (BUG checks) during DMA unmapping, which may lead to denial of service.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 4.9.316 · fixed in 4.10; From 4.14.281 · fixed in 4.15; From 4.19.245 · fixed in 4.20
- Linux Linux
5.2
- KernelLinux
From 5.2.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.2
References 5
Questions about CVE-2025-68745
What does this mean?
After the qla2xxx driver resets the chip while commands are still pending to the firmware, those commands get stuck and are never freed. A BUG_ON in the DMA unmap path can then trigger a kernel crash.Source: git.kernel.org
Am I affected, and how do I check?
The bug is in Linux kernel releases from 4.9.316 up to 4.10, 4.14.281 up to 4.15, 4.19.245 up to 4.20, 5.2.0 up to 6.6.160, 6.7.0 up to 6.12.114, and 6.13.0 up to 6.18.2. Check your kernel with uname -r, and check whether the qla2xxx driver is in use with lsmod | grep qla2xxx, since it only matters for QLogic Fibre Channel HBAs.Source: git.kernel.org
What should I do about it?
Upgrade to a kernel release with the fix: 6.6.160, 6.12.114, 6.18.2, or a later release in those branches, or to 4.10, 4.15, or 4.20 or later on the older 4.x branches. Use your distribution's kernel update to get a build that includes the fix.Source: git.kernel.org
Is it being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data