LiveActive security incident?Get immediate response
CVE Record

CVE-2025-38399: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port()

In the Linux kernel, the following vulnerability has been resolved: scsi: target: Fix NULL pointer dereference in core_scsi3_decode_spec_i_port() The function core_scsi3_decode_spec_i_port(), in its error code path, unconditionally calls core_scsi3_lunacl_undepend_item() passing the dest_se_deve pointer, which may be NULL. This can lead to a NULL pointer dereference if dest_se_deve remains unset. SPC-3 PR SPEC_I_PT: Unable to locate dest_tpg Unable to handle kernel paging request at virtual address dfff800000000012 Call trace: core_scsi3_lunacl_undepend_item+0x2c/0xf0 [target_core_mod] (P) core_scsi3_decode_spec_i_port+0x120c/0x1c30 [target_core_mod] core_scsi3_emulate_pro_register+0x6b8/0xcd8 [target_core_mod] target_scsi3_emulate_pr_out+0x56c/0x840 [target_core_mod] Fix this by adding a NULL check before calling core_scsi3_lunacl_undepend_item()

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A flaw in the Linux kernel’s SCSI target handling can crash the kernel when a persistent-reservation request reaches a specific error path. The documented impact is loss of availability, not data theft or modification. Systems acting as network-accessible SCSI targets warrant the greatest attention.

Executive priority

Treat this as a prompt availability remediation for exposed storage infrastructure, especially where an outage would disrupt critical workloads. Patch during the earliest safe maintenance window. Systems not providing Linux SCSI target services are lower priority after configuration verification.

Technical view

core_scsi3_decode_spec_i_port() may leave dest_se_deve unset after failing to locate dest_tpg, then pass that NULL pointer to core_scsi3_lunacl_undepend_item(). The resulting kernel paging fault can cause denial of service. The fix checks the pointer before calling the cleanup function. CVSS 3.1 is 7.5: network-accessible, low complexity, and availability-only impact.

Likely exposure

Exposure centers on Linux systems using the kernel SCSI target subsystem and processing SPC-3 persistent-reservation SPEC_I_PT requests. The bundle identifies multiple kernel versions from 5.9 through 6.16, but its version entries do not clearly distinguish vulnerable and corrected package boundaries. Confirm exact exposure through kernel or distribution guidance.

Exploitation context

The supplied record does not establish public proof-of-concept availability or active exploitation, and the CVE is not listed as KEV. The CVSS vector describes unauthenticated network reachability, but practical reachability depends on an accessible, configured Linux SCSI target path.

Researcher notes

The failure occurs during cleanup after destination resolution fails, making the NULL dereference the documented root cause. The source bundle supports denial of service only. Exact triggering prerequisites, distribution-specific affected ranges, exploit reliability, and broader consequences are not established and should not be inferred.

Mitigation direction

  • Update to a vendor-supported kernel containing the referenced NULL-check fix.
  • Prioritize network-accessible systems providing Linux SCSI target services.
  • If immediate patching is impossible, consult distribution guidance for supported temporary risk-reduction measures.

Validation and detection

  • Inventory deployed kernel versions and identify systems using the Linux SCSI target subsystem.
  • Compare each distribution package against its security advisory and the referenced stable fix commits.
  • Review kernel logs for dest_tpg lookup failures, paging requests, or target_core_mod crashes.
  • After updating, confirm the corrected kernel is active and test legitimate persistent-reservation operations.
Prepared
Confidence
medium
Sources
11

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2025-38399 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
10Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Linux

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2025-38399Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinuxf32ba612ef0f8eecaf6d2a5b04076ee7ea9ed039, f32ba612ef0f8eecaf6d2a5b04076ee7ea9ed039, f32ba612ef0f8eecaf6d2a5b04076ee7ea9ed039, f32ba612ef0f8eecaf6d2a5b04076ee7ea9ed039, f32ba612ef0f8eecaf6d2a5b04076ee7ea9ed039, f32ba612ef0f8eecaf6d2a5b04076ee7ea9ed039, f32ba612ef0f8eecaf6d2a5b04076ee7ea9ed039unaffected
LinuxLinux5.9, 0, 5.10.240, 5.15.187, 6.1.144, 6.6.97, 6.12.37, 6.15.6, 6.16affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.