CVE-2025-71238 is a double-free vulnerability in the Linux kernel SCSI qla2xxx driver, in drivers/scsi/qla2xxx/qla_bsg.c. The issue stems from inconsistent bsg_done() handling: while most routines call bsg_done() only on successful completion, some error paths also invoke it, causing the same resource to be freed twice. The bug was observed during vendor-specific BSG request processing, with crash traces involving sg_copy_buffer(), qla2x00_process_vendor_specific(), and qla24xx_bsg_request(). In affected kernels, this can lead to a kernel page fault and panic. The upstream fix adds validation before calling bsg_done() to prevent the duplicate free on failure paths.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Referenced as one of many CVEs addressed by SUSE kernel security updates; no vulnerability details are provided in the content.
A Linux kernel double-free vulnerability in the qla2xxx SCSI driver (drivers/scsi/qla2xxx/qla_bsg.c) where bsg_done() could be invoked on failure paths, leading to kernel panic or crash.
Listed as one of 206 vulnerabilities addressed by a SUSE kernel security update; no per-CVE technical detail is provided in the content.
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.