CVE-2025-38332
IBM lpfc String Buffer Overflow Vulnerability
Description
In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string.
INFO
Published Date :
July 10, 2025, 9:15 a.m.
Last Modified :
July 10, 2025, 1:17 p.m.
Source :
416baaa9-dc9f-4396-8d5f-8c081fb06d67
Remotely Exploitable :
No
Impact Score :
Exploitability Score :
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-38332.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-38332 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-38332 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
New CVE Received by 416baaa9-dc9f-4396-8d5f-8c081fb06d67
Jul. 10, 2025
Action Type Old Value New Value Added Description In the Linux kernel, the following vulnerability has been resolved: scsi: lpfc: Use memcpy() for BIOS version The strlcat() with FORTIFY support is triggering a panic because it thinks the target buffer will overflow although the correct target buffer size is passed in. Anyway, instead of memset() with 0 followed by a strlcat(), just use memcpy() and ensure that the resulting buffer is NULL terminated. BIOSVersion is only used for the lpfc_printf_log() which expects a properly terminated string. Added Reference https://git.kernel.org/stable/c/003baa7a1a152576d744bd655820449bbdb0248e Added Reference https://git.kernel.org/stable/c/2f63bf0d2b146956a2f2ff3b25cee71019e64561 Added Reference https://git.kernel.org/stable/c/34c0a670556b24d36c9f8934227edb819ca5609e Added Reference https://git.kernel.org/stable/c/75ea8375c5a83f46c47bfb3de6217c7589a8df93 Added Reference https://git.kernel.org/stable/c/ac7bfaa099ec3e4d7dfd0ab9726fc3bc7911365d Added Reference https://git.kernel.org/stable/c/ae82eaf4aeea060bb736c3e20c0568b67c701d7d Added Reference https://git.kernel.org/stable/c/b699bda5db818b684ff62d140defd6394f38f3d6 Added Reference https://git.kernel.org/stable/c/d34f2384d6df11a6c67039b612c2437f46e587e8
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-38332 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-38332
weaknesses.