CVE-2025-38332
What it is
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.
At a glance
- Exploitability
- Can be exploited locally on the machine with a low-privilege account. High risk of service disruption.
- Exploit odds
- 0.2% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 0.2% in the next 30 days (EPSS).
- Severity: 5.5 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 0.2% · EPSS, next 30 days
- Record status
- Analyzed
Affected
- Linux Kernel < 5.4.295
- Linux Kernel < 5.10.239
- Linux Kernel < 5.15.186
- Linux Kernel < 6.1.142
- Linux Kernel < 6.6.95
- Linux Kernel < 6.12.35
- Linux Kernel < 6.15.4
- Debian Linux 11.0
Attack profile CVSS 3.1 · 5.5
- Attack vector
- Local
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2025-38332.md and follow it. Check whether this project is affected by CVE-2025-38332. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- https://git.kernel.org/stable/c/003baa7a1a152576d744bd655820449bbdb0248e
- https://git.kernel.org/stable/c/2f63bf0d2b146956a2f2ff3b25cee71019e64561
- https://git.kernel.org/stable/c/34c0a670556b24d36c9f8934227edb819ca5609e
- https://git.kernel.org/stable/c/75ea8375c5a83f46c47bfb3de6217c7589a8df93
- https://git.kernel.org/stable/c/ac7bfaa099ec3e4d7dfd0ab9726fc3bc7911365d
- https://git.kernel.org/stable/c/ae82eaf4aeea060bb736c3e20c0568b67c701d7d
- https://git.kernel.org/stable/c/b699bda5db818b684ff62d140defd6394f38f3d6
- https://git.kernel.org/stable/c/d34f2384d6df11a6c67039b612c2437f46e587e8
References
- https://git.kernel.org/stable/c/003baa7a1a152576d744bd655820449bbdb0248e
- https://git.kernel.org/stable/c/2f63bf0d2b146956a2f2ff3b25cee71019e64561
- https://git.kernel.org/stable/c/34c0a670556b24d36c9f8934227edb819ca5609e
- https://git.kernel.org/stable/c/75ea8375c5a83f46c47bfb3de6217c7589a8df93
- https://git.kernel.org/stable/c/ac7bfaa099ec3e4d7dfd0ab9726fc3bc7911365d
- https://git.kernel.org/stable/c/ae82eaf4aeea060bb736c3e20c0568b67c701d7d
- https://git.kernel.org/stable/c/b699bda5db818b684ff62d140defd6394f38f3d6
- https://git.kernel.org/stable/c/d34f2384d6df11a6c67039b612c2437f46e587e8
- https://lists.debian.org/debian-lts-announce/2025/10/msg00007.html
- https://lists.debian.org/debian-lts-announce/2025/10/msg00008.html