CVE-2025-38695

scsi: lpfc: Check for hdwq null ptr when cleaning up lpfc_vport structure

MEDIUM
5.5
CVSS Score
Published: September 4, 2025 at 03:32 PM UTC
Updated: October 19, 2026 at 09:10 PM UTC
3 products affected across 3 vendorsLinux KernelDebian LinuxSIMATIC CN 4100

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.5
Exploit prediction
EPSS 0.2%

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

All versions5.1 ≤ v < 5.4.2975.11 ≤ v < 5.15.1905.16 ≤ v < 6.1.1495.5 ≤ v < 5.10.2416.13 ≤ v < 6.15.116.16 ≤ v < 6.16.26.2 ≤ v < 6.6.1036.7 ≤ v < 6.12.435.15e5b511d8bfaf765cb92a695cda336c936cb86dc
Vendor states this is fixed in 46a0602c24d7d425dd8e00c749cd64a934aac7ec (fixed)
Vendor states this is fixed in 571617f171f723b05f02d154a2e549a17eab4935 (fixed)
Vendor states this is fixed in 5e25ee1ecec91c61a8acf938ad338399cad464de (fixed)
Vendor states this is fixed in 6698796282e828733cde3329c887b4ae9e5545e9 (fixed)
Vendor states this is fixed in 6711ce7e9de4eb1a541ef30638df1294ea4267f8 (fixed)
Vendor states this is fixed in 74bdf54a847dab209d2a8f65852f59b7fa156175 (fixed)
Vendor states this is fixed in 7925dd68807cc8fd755b04ca99e7e6f1c04392e8 (fixed)
Vendor states this is fixed in add68606a01dcccf18837a53e85b85caf0693b4b (fixed)
Vendor states this is fixed in d3f55f46bb37a8ec73bfe3cfe36e3ecfa2945dfa (fixed)
Vendor states this is fixed in 5.1 (unaffected)
Vendor states this is fixed in 5.10.241 (unaffected)
Vendor states this is fixed in 5.15.190 (unaffected)
Vendor states this is fixed in 5.4.297 (unaffected)
Vendor states this is fixed in 6.1.149 (unaffected)
Vendor states this is fixed in 6.12.43 (unaffected)
Vendor states this is fixed in 6.15.11 (unaffected)
Vendor states this is fixed in 6.16.2 (unaffected)
Vendor states this is fixed in 6.17 (unaffected)
Vendor states this is fixed in 6.6.103 (unaffected)
v < V5.0
Affected range stops below V5.0, so it looks safe — our inference, not a vendor statement

References (12)

Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/46a0602c24d7d425dd8e00c749cd64a934aac7ec
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/571617f171f723b05f02d154a2e549a17eab4935
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/5e25ee1ecec91c61a8acf938ad338399cad464de
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6698796282e828733cde3329c887b4ae9e5545e9
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/6711ce7e9de4eb1a541ef30638df1294ea4267f8
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/74bdf54a847dab209d2a8f65852f59b7fa156175
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/7925dd68807cc8fd755b04ca99e7e6f1c04392e8
Patch
Source: 416baaa9-dc9f-4396-8d5f-8c081fb06d67
https://git.kernel.org/stable/c/add68606a01dcccf18837a53e85b85caf0693b4b

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-476

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card