Vulnerability · CVE-2025-38332
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 th
Published Jul 10, 2025 · catalog updated Jun 11, 2026 · Linux Linux
Check this week
CVE-2025-38332 is not in CISA KEV. FIRST estimates a 20.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Gaps on this record
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- None0.0
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 20.00%
- Remediation
- Version ranges on file
- Affected products
- vendor Linux Linux b3b4f3e1d575fe142fd437158425c2359b695ff1 <2f63bf0d2b146956a2f2ff3b25cee71019e64561
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.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- vendor Linux Linux b3b4f3e1d575fe142fd437158425c2359b695ff1 <2f63bf0d2b146956a2f2ff3b25cee71019e64561b3b4f3e1d575fe142fd437158425c2359b695ff1 <2f63bf0d2b146956a2f2ff3b25cee71019e64561
How to fix CVE-2025-38332
Recommended remediation
Affected version ranges suggest a fixed boundary. Verify against the vendor advisory for your release.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
CVE-2025-38332 is not in CISA KEV. FIRST estimates a 20.00% chance of exploitation in the next 30 days. Check whether you run Linux Linux.
Which versions are affected?
Compare what you have installed with Linux Linux b3b4f3e1d575fe142fd437158425c2359b695ff1 <2f63bf0d2b146956a2f2ff3b25cee71019e64561 b3b4f3e1d575fe142fd437158425c2359b695ff1 <2f63bf0d2b146956a2f2ff3b25cee71019e64561. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
No weakness class is stored. EPSS 20.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Jul 10, 2025 · EUVD
Detected
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 termin
Jun 11, 2026 · EUVD
Updated
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 termin
Sources
- EUVDVulnerability recordEUVD-2025-20914
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, i
euvd.enisa.europa.eu
References
Freshness
Last verified in this catalog Jun 11, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.