Loading vulnerability…
CVE-2025-38332 affects BIOS-version handling in the Linux kernel SCSI lpfc driver. The affected logic zero-initializes the BIOSVersion buffer and appends data using strlcat(). In kernels built with FORTIFY support, strlcat() can incorrectly identify the operation as a destination-buffer overflow despite being supplied the correct destination size, causing a kernel panic. The fix replaces the initialization-and-concatenation sequence with memcpy() and explicitly ensures NUL termination before BIOSVersion is passed to lpfc_printf_log().
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Linux kernel SCSI lpfc BIOS-version memory handling flaw.
Linux kernel lpfc SCSI driver flaw remediated by safely copying the BIOS version with memcpy().
A Linux kernel SCSI lpfc-driver flaw involving handling of the BIOS version, fixed by using memcpy().
Linux kernel SCSI lpfc driver flaw addressed by using memcpy() when handling the BIOS version.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.