Skip to main content
VulnerabilityPublished Updated

CVE-2025-71238: Linux kernel · scsi: qla2xxx: Fix bsg_done() causing double free

Affects Linux kernelSource CVE Database V5

0

Not known to be exploited · fixed in f2bbb4db0e4a4fbd5e649c0b5d8733f61da24720 : update Linux kernel when convenient.

Data as of 26 Oct 2026, 13:07 UTC

Severity
Unrated

Rated by Threat Radar · No CVSS score from NVD or the CNA

EPSS
0.2% chance of exploitation in 30 days – higher than 10% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CISA SSVC
Exploitation
No evidence of active exploitation and no public proof of concept
Automatable
Attackers cannot reliably automate steps 1–4 of the kill chain
Technical impact
Total control over the software or total information disclosure

CISA SSVC assessment, 2026-06-10.

Patch
Available – fixed in f2bbb4db0e4a4fbd5e649c0b5d8733f61da24720, c2c68225b1456f4d0d393b5a8778d51bb0d5b1d0, 708003e1bc857dd014d4c44278d7d77c26f91b1c +5

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 4 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
LinuxLinuxAffected
  • ≥ 1b81e7f3019d632a707e07927e946ffbbc102910, < f2bbb4db0e4a4fbd5e649c0b5d8733f61da24720
Fixed in
  • f2bbb4db0e4a4fbd5e649c0b5d8733f61da24720
LinuxLinuxAffected
  • ≥ 1b81e7f3019d632a707e07927e946ffbbc102910, < c2c68225b1456f4d0d393b5a8778d51bb0d5b1d0
Fixed in
  • c2c68225b1456f4d0d393b5a8778d51bb0d5b1d0
LinuxLinuxAffected
  • ≥ 1b81e7f3019d632a707e07927e946ffbbc102910, < 708003e1bc857dd014d4c44278d7d77c26f91b1c
Fixed in
  • 708003e1bc857dd014d4c44278d7d77c26f91b1c
LinuxLinuxAffected
  • ≥ 1b81e7f3019d632a707e07927e946ffbbc102910, < 871f6236da96c4a9712b8a29d7f555f767a47e95
Fixed in
  • 871f6236da96c4a9712b8a29d7f555f767a47e95
LinuxLinuxAffected
  • ≥ 1b81e7f3019d632a707e07927e946ffbbc102910, < 74e7458537cd9349cf019862e51491f670871707
Fixed in
  • 74e7458537cd9349cf019862e51491f670871707
LinuxLinuxAffected
  • ≥ 1b81e7f3019d632a707e07927e946ffbbc102910, < 057a5bdc481e58ab853117254867ffb22caf9f6e
Fixed in
  • 057a5bdc481e58ab853117254867ffb22caf9f6e

Description

In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Fix bsg_done() causing double free Kernel panic observed on system, [5353358.825191] BUG: unable to handle page fault for address: ff5f5e897b024000 [5353358.825194] #PF: supervisor write access in kernel mode [5353358.825195] #PF: error_code(0x0002) - not-present page [5353358.825196] PGD 100006067 P4D 0 [5353358.825198] Oops: 0002 [#1] PREEMPT SMP NOPTI [5353358.825200] CPU: 5 PID: 2132085 Comm: qlafwupdate.sub Kdump: loaded Tainted: G W L ------- --- 5.14.0-503.34.1.el9_5.x86_64 #1 [5353358.825203] Hardware name: HPE ProLiant DL360 Gen11/ProLiant DL360 Gen11, BIOS 2.44 01/17/2025 [5353358.825204] RIP: 0010:memcpy_erms+0x6/0x10 [5353358.825211] RSP: 0018:ff591da8f4f6b710 EFLAGS: 00010246 [5353358.825212] RAX: ff5f5e897b024000 RBX: 0000000000007090 RCX: 0000000000001000 [5353358.825213] RDX: 0000000000001000 RSI: ff591da8f4fed090 RDI: ff5f5e897b024000 [5353358.825214] RBP: 0000000000010000 R08: ff5f5e897b024000 R09: 0000000000000000 [5353358.825215] R10: ff46cf8c40517000 R11: 0000000000000001 R12: 0000000000008090 [5353358.825216] R13: ff591da8f4f6b720 R14: 0000000000001000 R15: 0000000000000000 [5353358.825218] FS: 00007f1e88d47740(0000) GS:ff46cf935f940000(0000) knlGS:0000000000000000 [5353358.825219] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [5353358.825220] CR2: ff5f5e897b024000 CR3: 0000000231532004 CR4: 0000000000771ef0 [5353358.825221] PKRU: 55555554 [5353358.825222] Call Trace: [5353358.825223] <TASK> [5353358.825224] ? show_trace_log_lvl+0x1c4/0x2df [5353358.825229] ? show_trace_log_lvl+0x1c4/0x2df [5353358.825232] ? sg_copy_buffer+0xc8/0x110 [5353358.825236] ? __die_body.cold+0x8/0xd [5353358.825238] ? page_fault_oops+0x134/0x170 [5353358.825242] ? kernelmode_fixup_or_oops+0x84/0x110 [5353358.825244] ? exc_page_fault+0xa8/0x150 [5353358.825247] ? asm_exc_page_fault+0x22/0x30 [5353358.825252] ? memcpy_erms+0x6/0x10 [5353358.825253] sg_copy_buffer+0xc8/0x110 [5353358.825259] qla2x00_process_vendor_specific+0x652/0x1320 [qla2xxx] [5353358.825317] qla24xx_bsg_request+0x1b2/0x2d0 [qla2xxx] Most routines in qla_bsg.c call bsg_done() only for success cases. However a few invoke it for failure case as well leading to a double free. Validate before calling bsg_done().

References

Community reviews

Loading reviews…