Loading vulnerability…
CVE-2025-38289 is a use-after-free vulnerability in the Linux kernel SCSI lpfc driver. The dev_loss_tmo_callbk callback can potentially access an ndlp object after its initial nodelist reference has been removed during lpfc driver unload or fatal-error handling. The fix reorders the relevant operations so the callback does not use the object after the reference-removal condition.
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.
5 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Linux kernel use-after-free vulnerability in the SCSI lpfc driver that can cause denial of service.
A potential use-after-free vulnerability in the Linux kernel lpfc SCSI driver’s dev_loss_tmo_callbk path. It can occur during driver unload or fatal-error handling when the initial nodelist reference has already been removed. The fix reorders code to prevent use of the freed ndlp object.
A Linux kernel vulnerability in scsi: lpfc that can lead to denial of service due to a use-after-free condition.
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.