CVE-2025-38332
scsi: lpfc: Use memcpy() for BIOS version
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
Version range not reported
- Linux Linux
5.2
References 8
git.kernel.org
- stable/c/ac7bfaa099ec3e4d7dfd0ab9726fc3bc7911365d
- stable/c/b699bda5db818b684ff62d140defd6394f38f3d6
- stable/c/d34f2384d6df11a6c67039b612c2437f46e587e8
- stable/c/75ea8375c5a83f46c47bfb3de6217c7589a8df93
- stable/c/34c0a670556b24d36c9f8934227edb819ca5609e
- stable/c/2f63bf0d2b146956a2f2ff3b25cee71019e64561
- stable/c/003baa7a1a152576d744bd655820449bbdb0248e
- stable/c/ae82eaf4aeea060bb736c3e20c0568b67c701d7d