LiveActive security incident?Get immediate response
CVE Record

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

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.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Linux systems using the qla2xxx QLogic Fibre Channel driver may retain storage commands after an adapter reset or crash during concurrent cleanup. This can interrupt storage-dependent workloads. The supplied record rates it critical at CVSS 9.8, although its narrative primarily substantiates availability impact rather than data theft or modification.

Executive priority

Prioritize urgent assessment and patching on storage servers using qla2xxx, especially systems supporting business-critical Fibre Channel workloads. Lower priority for hosts where the driver and relevant target functionality are absent. Treat service disruption as the substantiated business risk; the supplied sources do not establish data compromise or active attacks.

Technical view

After a qla2xxx chip reset, commands already sent to firmware can remain stuck because the firmware will never answer them. Concurrent CPUs can also race while unmapping command scatter-gather DMA state, triggering a kernel BUG. The referenced fix clears affected commands and reverts portions of the changes that introduced the cleanup problems.

Likely exposure

Exposure is limited to systems running affected Linux kernels with qla2xxx, particularly Fibre Channel target deployments encountering chip resets, offline ports, or host resets. The supplied version data is ambiguous and includes commit identifiers alongside releases, so distribution backports and fix-commit inclusion must be checked rather than relying solely on version numbers.

Exploitation context

The supplied record is not in KEV and provides no evidence of active exploitation. It describes reset and concurrency conditions, not a demonstrated remote attack path. Although the supplied CVSS vector states network access and full confidentiality, integrity, and availability impact, those impacts are not explained by the technical narrative.

Researcher notes

The strongest evidence supports improper command cleanup and a DMA-unmap race producing kernel BUG conditions. The supplied CVSS 9.8 vector appears broader than the described behavior, and affected-version encoding is unclear. Researchers should distinguish upstream commit ancestry from distribution backports and avoid inferring remote code execution or confidentiality impact without additional evidence.

Mitigation direction

  • Inventory hosts using qla2xxx, prioritizing Fibre Channel targets and systems experiencing adapter resets.
  • Apply a vendor-supported kernel containing the applicable stable fix; confirm using vendor guidance or referenced commits.
  • Until updated, minimize avoidable adapter resets and closely monitor critical storage workloads.
  • Escalate reset-related storage instability because command stalls or kernel crashes can disrupt dependent services.

Validation and detection

  • Confirm whether qla2xxx and SCSI target functionality are active on each host.
  • Map running kernels and distribution backports to the referenced stable fixes.
  • Review logs for qlt_free_cmd, dma_unmap_sg_attrs, stuck commands, adapter resets, and offline-port events.
  • After updating, test reset recovery in staging and confirm commands clear without kernel BUGs.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-68745 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Linux

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2025-68745Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxaefed3e5548f28e5fecafda6604fcbc65484dbaa, aefed3e5548f28e5fecafda6604fcbc65484dbaa, eb67b7a23d357f578578e737cb6412ae2384f352, ec9639d92c1e10d4bc667e842753d85e21683d5c, e6e957f552d5b696879a31e5b0e2a9120e1ea86e, 4.9.316, 4.14.281, 4.19.245unaffected
LinuxLinux5.2, 0, 6.18.2, 6.19affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.