Skip to main content
VulnerabilityPublished Updated

CVE-2025-38695: Linux kernel · scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure

Affects Linux kernelSource CVE Database V5

0
Compare

Not known to be exploited · fixed in d3f55f46bb37a8ec73bfe3cfe36e3ecfa2945dfa : 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 d3f55f46bb37a8ec73bfe3cfe36e3ecfa2945dfa, add68606a01dcccf18837a53e85b85caf0693b4b, 6698796282e828733cde3329c887b4ae9e5545e9 +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
  • ≥ 5e5b511d8bfaf765cb92a695cda336c936cb86dc, < d3f55f46bb37a8ec73bfe3cfe36e3ecfa2945dfa
Fixed in
  • d3f55f46bb37a8ec73bfe3cfe36e3ecfa2945dfa
LinuxLinuxAffected
  • ≥ 5e5b511d8bfaf765cb92a695cda336c936cb86dc, < add68606a01dcccf18837a53e85b85caf0693b4b
Fixed in
  • add68606a01dcccf18837a53e85b85caf0693b4b
LinuxLinuxAffected
  • ≥ 5e5b511d8bfaf765cb92a695cda336c936cb86dc, < 6698796282e828733cde3329c887b4ae9e5545e9
Fixed in
  • 6698796282e828733cde3329c887b4ae9e5545e9
LinuxLinuxAffected
  • ≥ 5e5b511d8bfaf765cb92a695cda336c936cb86dc, < 571617f171f723b05f02d154a2e549a17eab4935
Fixed in
  • 571617f171f723b05f02d154a2e549a17eab4935
LinuxLinuxAffected
  • ≥ 5e5b511d8bfaf765cb92a695cda336c936cb86dc, < 7925dd68807cc8fd755b04ca99e7e6f1c04392e8
Fixed in
  • 7925dd68807cc8fd755b04ca99e7e6f1c04392e8
LinuxLinuxAffected
  • ≥ 5e5b511d8bfaf765cb92a695cda336c936cb86dc, < 6711ce7e9de4eb1a541ef30638df1294ea4267f8
Fixed in
  • 6711ce7e9de4eb1a541ef30638df1294ea4267f8

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure If a call to lpfc_sli4_read_rev() from lpfc_sli4_hba_setup() fails, the resultant cleanup routine lpfc_sli4_vport_delete_fcp_xri_aborted() may occur before sli4_hba.hdwqs are allocated. This may result in a null pointer dereference when attempting to take the abts_io_buf_list_lock for the first hardware queue. Fix by adding a null ptr check on phba->sli4_hba.hdwq and early return because this situation means there must have been an error during port initialization.

References

Community reviews

Loading reviews…