CVE-2025-68745

A flaw was found in the Linux kernel's qla2xxx SCSI driver. This vulnerability occurs when commands sent to the firmware (FW) are not properly cleared after a chip reset. A local attacker could exploit a race condition during direct memory access (DMA) unmapping, leading to a kernel panic. This can result in a system crash and a Denial of Service (DoS).

A moderate flaw was found in the Linux kernel's qla2xxx SCSI driver, affecting the kernel and kernel-rt components in Red Hat Enterprise Linux 8, 9, and 10. Commands sent to the firmware were not properly cleared after a chip reset, and a race condition between two CPUs concurrently performing DMA unmapping in qlt_unmap_sg() could trigger a kernel BUG_ON, resulting in a kernel panic. A local attacker able to trigger the chip reset and racing DMA unmap paths could exploit this condition to crash the system, causing a denial of service; confidentiality and integrity are not impacted. Red Hat Enterprise Linux 7 Extended Lifecycle Support and Red Hat In-Vehicle OS 1 are not affected because the vulnerable code is not present in those releases. Fixes for the affected Red Hat Enterprise Linux 8, 9, and 10 streams are being pursued by the Red Hat kernel team, and updates have already shipped or are in progress for several streams. Red Hat rates this flaw Moderate severity with a CVSS 4.7 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H), which differs significantly from the Critical 9.8 score in the upstream CVE record. The upstream score reflects a network-reachable vector with full confidentiality, integrity, and availability impact that is not supported by the technical evidence: exploitation requires local access and a high-complexity race condition, and only availability is affected.

The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.

To mitigate this issue, if the qla2xxx SCSI driver is not required, it can be prevented from loading by blacklisting the module. This can be achieved by creating a modprobe configuration file.

1. Create a file named /etc/modprobe.d/blacklist-qla2xxx.conf with the following content:

blacklist qla2xxx
install qla2xxx /bin/true

2. Rebuild the initial ramdisk:

dracut -f -v

3. Reboot the system for the changes to take effect.

This mitigation will prevent the qla2xxx module from loading, which may impact systems relying on QLogic Fibre Channel HBAs. A system reboot is required for the changes to take full effect.