CVE-2025-38700
BaseFortify
Publication date: 2025-09-04
Last updated on: 2025-11-03
Assigner: kernel.org
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| linux | kernel | 6.1.153 |
| linux | kernel | 5.10.244 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability occurs in the Linux kernel's SCSI iSCSI library (libiscsi). When setting up iSER (iSCSI Extensions for RDMA), if the allocation of ib_fast_reg_mr memory fails, the system still initializes a pointer (iscsi_conn->dd_data) without verifying that memory was actually allocated. This leads to an invalid pointer dereference during connection teardown, causing the machine to panic (crash). The fix ensures that iscsi_conn->dd_data is only initialized if memory allocation succeeds.
How can this vulnerability impact me? :
This vulnerability can cause a system panic (crash) in the Linux kernel when the iSER setup fails to allocate necessary memory. This can lead to denial of service as the affected machine may become unresponsive or reboot unexpectedly due to the kernel panic triggered by the invalid pointer dereference.
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 kernel panic messages related to iscsi and ib_fast_reg_mr allocation failures. Specifically, look for panic traces containing messages like 'iser_create_fastreg_desc: Failed to allocate ib_fast_reg_mr err=-12' and 'BUG: unable to handle page fault for address'. Commands such as 'dmesg | grep -i iser' or 'journalctl -k | grep -i iscsi' can help identify these panic messages in the logs.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation involves updating the Linux kernel to a version where the iscsi libiscsi code initializes iscsi_conn->dd_data only if memory is allocated, thus preventing the panic. Until an update is applied, monitoring for the panic conditions and avoiding workloads that trigger iSER setup failures may reduce risk.