CVE-2025-68745Network attack vector

Kernel crash or command hang after chip reset

Published Dec 24, 2025 · Updated Dec 24, 2025

A reset-path flaw in affected Linux qla2xxx kernels allows attackers to hang firmware commands or crash the kernel during chip reset. The __qla2x00_abort_all_cmds path left pre-reset commands allocated although firmware would never answer, while competing CPUs could both unmap one command and trigger a BUG_ON. Reachability requires the qla2xxx target driver, a chip reset, and, for the crash path, a concurrent qlt_unmap_sg race; outcomes are stuck I/O or a kernel crash.

CVSS severity9.8
Critical
EPSS probability0.36%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

A reset-path flaw in affected Linux qla2xxx kernels allows attackers to hang firmware commands or crash the kernel during chip reset. The __qla2x00_abort_all_cmds path left pre-reset commands allocated although firmware would never answer, while competing CPUs could both unmap one command and trigger a BUG_ON. Reachability requires the qla2xxx target driver, a chip reset, and, for the crash path, a concurrent qlt_unmap_sg race; outcomes are stuck I/O or a kernel crash.

The record

CVE
CVE-2025-68745
Published
Dec 24, 2025
Updated
Dec 24, 2025
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
network
Privileges
unauthenticated

Timeline

How it unfolded

  1. Dec 24, 2025CVE publishedPublication date reported by the CVE source.
  2. Dec 24, 2025Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=5.2
  2. Affected versionversion=aefed3e5548f28e5fecafda6604fcbc65484dbaa <5c1fb3fd05da3d55b8cbc42d7d660b313cbdc936
  3. Affected versionversion=aefed3e5548f28e5fecafda6604fcbc65484dbaa <d46c69a087aa3d1513f7a78f871b80251ea0c1ae
  4. Affected versionversion=e6e957f552d5b696879a31e5b0e2a9120e1ea86e
  5. Affected versionversion=eb67b7a23d357f578578e737cb6412ae2384f352
  6. Affected versionversion=ec9639d92c1e10d4bc667e842753d85e21683d5c

What conditions does exploitation require?

Attack vectornetwork
Required privilegesunauthenticated

What is affected?

The Linux Kernel Organization · Linuxversion=5.2; version=aefed3e5548f28e5fecafda6604fcbc65484dbaa <5c1fb3fd05da3d55b8cbc42d7d660b313cbdc936; version=aefed3e5548f28e5fecafda6604fcbc65484dbaa <d46c69a087aa3d1513f7a78f871b80251ea0c1ae; version=e6e957f552d5b696879a31e5b0e2a9120e1ea86e; version=eb67b7a23d357f578578e737cb6412ae2384f352; version=ec9639d92c1e10d4bc667e842753d85e21683d5c

Published CVSS scores

9.8Linux kernel CNACVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesunauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo