In the Linux kernel, the following vulnerability has been resolved:
scsi: target: target_core_configfs: Add length check to avoid buffer overflow
A buffer overflow arises from the usage of snprintf to write into the
buffer "buf" in target_lu_gp_members_show function located in
/drivers/target/target_core_configfs.c. This buffer is allocated with
size LU_GROUP_NAME_BUF (256 bytes).
snprintf(...) formats multiple strings into buf with the HBA name
(hba->hba_group.cg_item), a slash character, a devicename (dev->
dev_group.cg_item) and a newline character, the total formatted string
length may exceed the buffer size of 256 bytes.
Since snprintf() returns the total number of bytes that would have been
written (the length of %s/%sn ), this value may exceed the buffer length
(256 bytes) passed to memcpy(), this will ultimately cause function
memcpy reporting a buffer overflow error.
An additional check of the return value of snprintf() can avoid this
buffer overflow.
Security readout for executives and security teams
Plain-English summary
A Linux kernel flaw in the SCSI target configuration interface can mishandle unusually long storage object names. A locally authenticated user with low privileges may trigger kernel memory disclosure or a crash, potentially exposing sensitive information or disrupting storage services. Risk is concentrated on systems using the affected SCSI target functionality, rather than all Linux hosts equally.
Executive priority
Treat this as a high-priority patch for exposed storage infrastructure because a successful local attack could disclose kernel information or interrupt storage availability. Apply normal accelerated remediation rather than emergency internet-wide response: the supplied evidence indicates local access is required and does not establish active exploitation.
Technical view
target_lu_gp_members_show() formats HBA and device names into a 256-byte buffer. snprintf() may return the larger length that would have been written; using that value in memcpy() can exceed the valid buffer contents. The supplied CVSS 3.1 score is 7.1, with local access, low complexity, low privileges, no user interaction, and high confidentiality and availability impact.
Likely exposure
Prioritize Linux storage servers, appliances, and virtualization hosts that enable the kernel SCSI target and its configfs management interface. Practical exposure requires local access and interaction with the affected functionality. The supplied version data is broad and does not provide a reliable distribution-package mapping, so confirm status against vendor kernel advisories or the referenced stable fixes.
Exploitation context
The source bundle does not identify public exploitation, and the CVE is not listed as KEV in the supplied data. The CVSS vector describes local, low-privilege exploitation with no user interaction. Evidence supports potential information disclosure and denial of service, but does not establish remote exploitation, code execution, or exploitation in the wild.
Researcher notes
The affected-version list contains repeated commit identifiers and ambiguous version entries, limiting precise branch assessment. Validate using distribution backport records or presence of the stable fix, not version strings alone. The provided record names no CWE and supplies no evidence of weaponization. Avoid inferring remote reachability or arbitrary code execution from the buffer-overflow description.
Mitigation direction
Update to a vendor-supported kernel containing the referenced length-check fix.
Prioritize storage and virtualization hosts using the kernel SCSI target subsystem.
Check distribution or appliance vendor guidance for package-specific fixed versions.
Restrict local accounts and administrative access to storage configuration interfaces until patched.
Validation and detection
Inventory kernel versions on systems providing Linux SCSI target services.
Determine whether the target subsystem and configfs management interface are enabled or used.
Compare kernel source or vendor packages with the referenced stable fix commits.
Reboot after updating and verify the running kernel matches the corrected package.
Review local access controls for users able to interact with storage configuration.
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-39998 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
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
0ADP 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.