LiveActive security incident?Get immediate response
CVE Record

CVE-2025-68818: scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path"

In the Linux kernel, the following vulnerability has been resolved: scsi: Revert "scsi: qla2xxx: Perform lockless command completion in abort path" This reverts commit 0367076b0817d5c75dfb83001ce7ce5c64d803a9. The commit being reverted added code to __qla2x00_abort_all_cmds() to call sp->done() without holding a spinlock. But unlike the older code below it, this new code failed to check sp->cmd_type and just assumed TYPE_SRB, which results in a jump to an invalid pointer in target-mode with TYPE_TGT_CMD: qla2xxx [0000:65:00.0]-d034:8: qla24xx_do_nack_work create sess success 0000000009f7a79b qla2xxx [0000:65:00.0]-5003:8: ISP System Error - mbx1=1ff5h mbx2=10h mbx3=0h mbx4=0h mbx5=191h mbx6=0h mbx7=0h. qla2xxx [0000:65:00.0]-d01e:8: -> fwdump no buffer qla2xxx [0000:65:00.0]-f03a:8: qla_target(0): System error async event 0x8002 occurred qla2xxx [0000:65:00.0]-00af:8: Performing ISP error recovery - ha=0000000058183fda. BUG: kernel NULL pointer dereference, address: 0000000000000000 PF: supervisor instruction fetch in kernel mode PF: error_code(0x0010) - not-present page PGD 0 P4D 0 Oops: 0010 [#1] SMP CPU: 2 PID: 9446 Comm: qla2xxx_8_dpc Tainted: G O 6.1.133 #1 Hardware name: Supermicro Super Server/X11SPL-F, BIOS 4.2 12/15/2023 RIP: 0010:0x0 Code: Unable to access opcode bytes at 0xffffffffffffffd6. RSP: 0018:ffffc90001f93dc8 EFLAGS: 00010206 RAX: 0000000000000282 RBX: 0000000000000355 RCX: ffff88810d16a000 RDX: ffff88810dbadaa8 RSI: 0000000000080000 RDI: ffff888169dc38c0 RBP: ffff888169dc38c0 R08: 0000000000000001 R09: 0000000000000045 R10: ffffffffa034bdf0 R11: 0000000000000000 R12: ffff88810800bb40 R13: 0000000000001aa8 R14: ffff888100136610 R15: ffff8881070f7400 FS: 0000000000000000(0000) GS:ffff88bf80080000(0000) knlGS:0000000000000000 CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 CR2: ffffffffffffffd6 CR3: 000000010c8ff006 CR4: 00000000003706e0 DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000 DR3: 0000000000000000 DR6: 00000000fffe0ff0 DR7: 0000000000000400 Call Trace: <TASK> ? __die+0x4d/0x8b ? page_fault_oops+0x91/0x180 ? trace_buffer_unlock_commit_regs+0x38/0x1a0 ? exc_page_fault+0x391/0x5e0 ? asm_exc_page_fault+0x22/0x30 __qla2x00_abort_all_cmds+0xcb/0x3e0 [qla2xxx_scst] qla2x00_abort_all_cmds+0x50/0x70 [qla2xxx_scst] qla2x00_abort_isp_cleanup+0x3b7/0x4b0 [qla2xxx_scst] qla2x00_abort_isp+0xfd/0x860 [qla2xxx_scst] qla2x00_do_dpc+0x581/0xa40 [qla2xxx_scst] kthread+0xa8/0xd0 </TASK> Then commit 4475afa2646d ("scsi: qla2xxx: Complete command early within lock") added the spinlock back, because not having the lock caused a race and a crash. But qla2x00_abort_srb() in the switch below already checks for qla2x00_chip_is_down() and handles it the same way, so the code above the switch is now redundant and still buggy in target-mode. Remove it.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2025-68818 is a Linux kernel storage-driver crash condition in the qla2xxx SCSI path. In a specific target-mode abort path, the driver can jump through an invalid pointer and trigger a kernel NULL pointer dereference. The business risk is service disruption on affected Linux systems using this driver, not confirmed remote compromise.

Executive priority

Handle as a targeted availability issue for storage infrastructure. Prioritize systems where Linux hosts provide or depend on qla2xxx-based storage connectivity, especially production storage paths, but do not treat it as internet-wide emergency based on current evidence.

Technical view

A prior qla2xxx change called sp->done() in __qla2x00_abort_all_cmds() without validating sp->cmd_type. In target-mode TYPE_TGT_CMD handling, that assumption can produce an invalid function-pointer jump and kernel oops during ISP error recovery. The resolved change removes the redundant buggy path by reverting the earlier lockless command-completion behavior.

Likely exposure

Exposure appears limited to Linux systems running affected kernel builds with the qla2xxx SCSI driver in relevant storage target-mode/error-recovery paths. General Linux systems without this driver or hardware path are unlikely to be exposed based on the supplied sources.

Exploitation context

The supplied bundle does not show CISA KEV listing or active exploitation. The evidence describes a crash observed during qla2xxx target-mode error recovery, so treat this primarily as an availability risk unless vendor advisories state otherwise.

Researcher notes

Key evidence is the kernel description: commit 0367076b0817d introduced a lockless abort-path completion assumption that failed for TYPE_TGT_CMD. Later locking work did not remove the target-mode bug; the resolution removes redundant buggy code. No CVSS, CWE, or exploit confirmation is supplied.

Mitigation direction

  • Apply vendor kernel updates that include the referenced stable qla2xxx fixes.
  • Check Linux distribution advisories for backported fixes matching deployed kernel packages.
  • For Siemens-managed environments, review the linked ProductCERT advisory for product-specific guidance.
  • Prioritize storage hosts using qla2xxx target-mode or affected Fibre Channel paths.
  • Avoid assuming mitigation details beyond vendor-published kernel guidance.

Validation and detection

  • Inventory Linux hosts for affected kernel versions and qla2xxx driver use.
  • Confirm whether qla2xxx target-mode or SCST-related deployments exist.
  • Check package changelogs for the referenced stable commit identifiers.
  • Review kernel logs for qla2xxx ISP errors, abort recovery, or NULL dereference traces.
  • Validate patched kernels in storage test environments before production rollout.
Prepared
Confidence
medium
Sources
10

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-68818 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

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

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.

ADP provider summaries

siemens-SADPADP container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux231cfa78ec5badd84a1a2b09465bfad1a926aba1, d6f7377528d2abf338e504126e44439541be8f7d, cd0a1804ac5bab2545ac700c8d0fe9ae9284c567, 0367076b0817d5c75dfb83001ce7ce5c64d803a9, 0367076b0817d5c75dfb83001ce7ce5c64d803a9, 0367076b0817d5c75dfb83001ce7ce5c64d803a9, 0367076b0817d5c75dfb83001ce7ce5c64d803a9, 9189f20b4c5307c0998682bb522e481b4567a8b8, 415d614344a4f1bbddf55d724fc7eb9ef4b39aad, 5.10.177, 5.15.105, 6.1.22, 5.4.240, 6.2.9unaffected
LinuxLinux6.3, 0, 5.10.248, 5.15.198, 6.1.160, 6.6.120, 6.12.64, 6.18.3, 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.