Kernel panic via fortified BIOS string concatenation
Published Jul 10, 2025 · Updated Jun 11, 2026
Denial of service in the Linux kernel lpfc driver allows local users to panic the kernel while adapter BIOS data is logged. In drivers/scsi/lpfc/lpfc_sli.c, a zeroed BIOSVersion buffer is passed to fortified strlcat(), whose object-size check reports an overflow and triggers the panic despite the correct size argument. Reachability requires execution of the lpfc BIOS-version logging path in a FORTIFY-enabled kernel; the consequence is a host-wide service interrupt rather than data disclosure or modification.
Summary
What happened
Denial of service in the Linux kernel lpfc driver allows local users to panic the kernel while adapter BIOS data is logged. In drivers/scsi/lpfc/lpfc_sli.c, a zeroed BIOSVersion buffer is passed to fortified strlcat(), whose object-size check reports an overflow and triggers the panic despite the correct size argument. Reachability requires execution of the lpfc BIOS-version logging path in a FORTIFY-enabled kernel; the consequence is a host-wide service interrupt rather than data disclosure or modification.
The record
- CVE
- CVE-2025-38332
- Published
- Jul 10, 2025
- Updated
- Jun 11, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux
- Classifications
- T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 10, 2025CVE publishedPublication date reported by the CVE source.
- Jun 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.2
- Affected versionversion=b3b4f3e1d575fe142fd437158425c2359b695ff1 <003baa7a1a152576d744bd655820449bbdb0248e
- Affected versionversion=b3b4f3e1d575fe142fd437158425c2359b695ff1 <2f63bf0d2b146956a2f2ff3b25cee71019e64561
- Affected versionversion=b3b4f3e1d575fe142fd437158425c2359b695ff1 <34c0a670556b24d36c9f8934227edb819ca5609e
- Affected versionversion=b3b4f3e1d575fe142fd437158425c2359b695ff1 <75ea8375c5a83f46c47bfb3de6217c7589a8df93
- Affected versionversion=b3b4f3e1d575fe142fd437158425c2359b695ff1 <ac7bfaa099ec3e4d7dfd0ab9726fc3bc7911365d
- Affected versionversion=b3b4f3e1d575fe142fd437158425c2359b695ff1 <ae82eaf4aeea060bb736c3e20c0568b67c701d7d
- Affected versionversion=b3b4f3e1d575fe142fd437158425c2359b695ff1 <b699bda5db818b684ff62d140defd6394f38f3d6
- Affected versionversion=b3b4f3e1d575fe142fd437158425c2359b695ff1 <d34f2384d6df11a6c67039b612c2437f46e587e8
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo