Loading vulnerability…
CVE-2025-38332 affects BIOS-version string handling in the Linux kernel's lpfc SCSI driver. A FORTIFY-enabled strlcat() operation incorrectly detects a destination-buffer overflow and triggers a kernel panic even though the correct destination-buffer size is supplied. The affected code zero-initializes the buffer with memset() before concatenating the BIOS version. The correction replaces this sequence with memcpy() and explicit NUL termination, preserving the terminated string required by 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.
17 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in the Linux kernel's lpfc SCSI driver can trigger a kernel panic when FORTIFY checks incorrectly identify a buffer overflow during BIOS-version string construction, affecting availability. The fix replaces memset() and strlcat() with memcpy() and ensures null termination. The advisory assigns a CVSS v3 base score of 5.5 and recommends updating Echo linux packages to version 6.1.147-1 or later.
A Linux kernel SCSI LPFC driver vulnerability addressed by changing BIOS-version handling to use memcpy().
Linux kernel SCSI lpfc BIOS-version memory handling flaw.
Linux kernel lpfc SCSI driver flaw remediated by safely copying the BIOS version with memcpy().
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.