Skip to main content
VulnerabilityPublished Updated

CVE-2025-68745: Linux kernel · scsi: qla2xxx: Clear cmds after chip reset

Source GCVE Database

0
Authoritative record:CVE-2025-68745· Critical 9.8

Not known to be exploited · CVSS 9.8 Critical · fixed in d46c69a087aa3d1513f7a78f871b80251ea0c1ae : patch Linux kernel as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in d46c69a087aa3d1513f7a78f871b80251ea0c1ae, c82c0fbb97d0fd44324eb55ab758408c7c964b32, 5c1fb3fd05da3d55b8cbc42d7d660b313cbdc936 +4
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 24 Dec 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • >=4.9.316 <4.10
  • >=4.14.281 <4.15
  • >=4.19.245 <4.20
Fixed in
  • d46c69a087aa3d1513f7a78f871b80251ea0c1ae
  • c82c0fbb97d0fd44324eb55ab758408c7c964b32
  • 5c1fb3fd05da3d55b8cbc42d7d660b313cbdc936
  • 4.20
  • 4.15
  • 4.10
  • 0d0a1a267c1ee7c41aeffdca84afcb113787a91a
LinuxLinuxAffected
  • =5.2
Fixed in–

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.

References

Community reviews

Loading reviews…