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 thinks the target buffer will overflow although the correct target buffer…
Does this matter?
Lower severity and a low EPSS score (0.18%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 5.5 MEDIUMCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 0.18% probability · 8th percentile
- CISA KEV
- Not listed
- Affected
- linux/linux kernel · debian/debian linux
- Source
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
References
- https://git.kernel.org/stable/c/003baa7a1a152576d744bd655820449bbdb0248ePatch
- https://git.kernel.org/stable/c/2f63bf0d2b146956a2f2ff3b25cee71019e64561Patch
- https://git.kernel.org/stable/c/34c0a670556b24d36c9f8934227edb819ca5609ePatch
- https://git.kernel.org/stable/c/75ea8375c5a83f46c47bfb3de6217c7589a8df93Patch
- https://git.kernel.org/stable/c/ac7bfaa099ec3e4d7dfd0ab9726fc3bc7911365dPatch
- https://git.kernel.org/stable/c/ae82eaf4aeea060bb736c3e20c0568b67c701d7dPatch
- https://git.kernel.org/stable/c/b699bda5db818b684ff62d140defd6394f38f3d6Patch
- https://git.kernel.org/stable/c/d34f2384d6df11a6c67039b612c2437f46e587e8Patch
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.htmlThird Party Advisory
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.htmlThird Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.