CVE-2025-68745
Description
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).
Mitigation
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 qla2xxx2. Rebuild the initial ramdisk:
install qla2xxx /bin/true
bash3. Reboot the system for the changes to take effect.
dracut -f -v
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.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
The following CVSS metrics and score provided are preliminary and subject to review.
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 4.7 | N/A | 9.8 |
| Attack Vector | Local | N/A | Network |
| Attack Complexity | High | N/A | Low |
| Privileges Required | Low | N/A | None |
| User Interaction | None | N/A | None |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | None | N/A | High |
| Integrity Impact | None | N/A | High |
| Availability Impact | High | N/A | High |
Vector
Red Hat: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H
cve.org: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Understanding the Weakness (CWE)
Integrity,Other
Technical Impact: Alter Execution Logic; Unexpected State
The main problem is that -- if a lock is overcome -- data could be altered in a bad state.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
