CVE-2025-71232
BaseFortify
Publication date: 2026-02-18
Last updated on: 2026-03-18
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 6.19 (inc) to 6.19.1 (exc) |
| linux | linux_kernel | From 5.16 (inc) to 6.1.164 (exc) |
| linux | linux_kernel | From 5.11 (inc) to 5.15.201 (exc) |
| linux | linux_kernel | From 6.2 (inc) to 6.6.125 (exc) |
| linux | linux_kernel | From 6.7 (inc) to 6.12.72 (exc) |
| linux | linux_kernel | From 6.13 (inc) to 6.18.11 (exc) |
| linux | linux_kernel | From 4.16 (inc) to 5.10.251 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-772 | The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is related to the Linux kernel's qla2xxx SCSI driver. It involves a system crash that occurs during repeated load and unload tests of the driver module. The crash is caused by improper handling of memory objects in the error path, specifically a failure to free certain objects, which leads to leftover objects in the slab cache during module shutdown.
The issue manifests as a kernel crash with warnings about slab cache objects still present when the qla2xxx module is being unloaded. The fix involves freeing the sp (service parameter or related object) in the error path to prevent the system crash.
How can this vulnerability impact me? :
This vulnerability can cause the Linux system to crash when the qla2xxx driver module is repeatedly loaded and unloaded, potentially leading to system instability or downtime.
Such crashes can disrupt normal operations, especially on systems relying on the affected SCSI driver for storage connectivity, which may result in data unavailability or loss of service.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by monitoring the system logs for specific error messages related to the qla2xxx driver. Look for kernel messages indicating a system crash or warnings such as 'BUG qla2xxx_srbs', 'kmem_cache_destroy qla2xxx_srbs: Slab cache still has objects', or messages about disabling MSI-X and kernel taint.
You can use the following commands to check for these signs:
- dmesg | grep qla2xxx
- journalctl -k | grep qla2xxx
- grep -i 'BUG qla2xxx_srbs' /var/log/messages
- grep -i 'kmem_cache_destroy qla2xxx_srbs' /var/log/messages
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version where the qla2xxx driver has been fixed to properly free memory in the error path, preventing system crashes.
Until the update is applied, avoid repeatedly loading and unloading the qla2xxx module in a loop, as this triggers the crash.
Monitor system logs for related errors and consider disabling or unloading the qla2xxx driver if it is not essential for your system's operation.