Skip to main content
VulnerabilityPublished Updated

CVE-2025-38700: Linux kernel · scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in fd5aad080edb501ab5c84b7623d612d0e3033403 : update Linux kernel when convenient.

Data as of 5 Nov 2026, 21:34 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

Thin evidence

One scorer or none
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Limited control over the software or limited information exposure

CISA SSVC assessment, 2026-11-05.

Patch
Available – fixed in fd5aad080edb501ab5c84b7623d612d0e3033403, f53af99f441ee79599d8df6113a7144d74cf9153, a145c269dc5380c063a20a0db7e6df2995962e9d +6

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Sep 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 5 Nov 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 5d91e209fb21fb9cc765729d4c6a85a9fb6c9187, < fd5aad080edb501ab5c84b7623d612d0e3033403
Fixed in
  • fd5aad080edb501ab5c84b7623d612d0e3033403
LinuxLinuxAffected
  • ≥ 5d91e209fb21fb9cc765729d4c6a85a9fb6c9187, < f53af99f441ee79599d8df6113a7144d74cf9153
Fixed in
  • f53af99f441ee79599d8df6113a7144d74cf9153
LinuxLinuxAffected
  • ≥ 5d91e209fb21fb9cc765729d4c6a85a9fb6c9187, < a145c269dc5380c063a20a0db7e6df2995962e9d
Fixed in
  • a145c269dc5380c063a20a0db7e6df2995962e9d
LinuxLinuxAffected
  • ≥ 5d91e209fb21fb9cc765729d4c6a85a9fb6c9187, < a33d42b7fc24fe03f239fbb0880dd5b4b4b97c19
Fixed in
  • a33d42b7fc24fe03f239fbb0880dd5b4b4b97c19
LinuxLinuxAffected
  • ≥ 5d91e209fb21fb9cc765729d4c6a85a9fb6c9187, < 35782c32528d82aa21f84cb5ceb2abd3526a8159
Fixed in
  • 35782c32528d82aa21f84cb5ceb2abd3526a8159
LinuxLinuxAffected
  • ≥ 5d91e209fb21fb9cc765729d4c6a85a9fb6c9187, < 66a373f50b4249d57f5a88c7be9676f9d5884865
Fixed in
  • 66a373f50b4249d57f5a88c7be9676f9d5884865

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: libiscsi: Initialize iscsi_conn->dd_data only if memory is allocated In case of an ib_fast_reg_mr allocation failure during iSER setup, the machine hits a panic because iscsi_conn->dd_data is initialized unconditionally, even when no memory is allocated (dd_size == 0). This leads invalid pointer dereference during connection teardown. Fix by setting iscsi_conn->dd_data only if memory is actually allocated. Panic trace: ------------ iser: iser_create_fastreg_desc: Failed to allocate ib_fast_reg_mr err=-12 iser: iser_alloc_rx_descriptors: failed allocating rx descriptors / data buffers BUG: unable to handle page fault for address: fffffffffffffff8 RIP: 0010:swake_up_locked.part.5+0xa/0x40 Call Trace: complete+0x31/0x40 iscsi_iser_conn_stop+0x88/0xb0 [ib_iser] iscsi_stop_conn+0x66/0xc0 [scsi_transport_iscsi] iscsi_if_stop_conn+0x14a/0x150 [scsi_transport_iscsi] iscsi_if_rx+0x1135/0x1834 [scsi_transport_iscsi] ? netlink_lookup+0x12f/0x1b0 ? netlink_deliver_tap+0x2c/0x200 netlink_unicast+0x1ab/0x280 netlink_sendmsg+0x257/0x4f0 ? _copy_from_user+0x29/0x60 sock_sendmsg+0x5f/0x70

References

Community reviews

Loading reviews…