CVE-2025-38289
BaseFortify
Publication date: 2025-07-10
Last updated on: 2025-11-19
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
| linux | linux_kernel | From 5.15.160 (inc) to 5.16 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-416 | The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a potential use-after-free issue in the Linux kernel's SCSI lpfc driver. Specifically, it involves the ndlp object in the dev_loss_tmo_callbk function, which can be accessed after it has been freed during driver unload or fatal error handling. The issue was detected by Smatch and fixed by reordering code to prevent accessing the ndlp object after its reference has been removed.
How can this vulnerability impact me? :
The vulnerability could lead to use-after-free conditions in the Linux kernel's SCSI lpfc driver, potentially causing system instability, crashes, or other unpredictable behavior during driver unload or error handling. This could affect system reliability and availability.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update the Linux kernel to a version that includes the fix for the use-after-free issue in the lpfc driver (scsi: lpfc). This fix involves reordering code to avoid the potential use-after-free during driver unload or fatal error handling. Until the update is applied, avoid unloading the lpfc driver or triggering fatal error handling scenarios that could expose the vulnerability.