CVE-2025-71238

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-03-04. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

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] [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().

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
9%
KEV
Not listed

Published

March 4, 2026

Last Modified

June 17, 2026

Advisory Details (8)

Auto-updated Aug 2, 2026
No patch confirmed yet.
generic

scsi: qla2xxx: Fix bsg_done() causing double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f2bbb4db0e4a4fbd5e649c0b5d8733f61da24720
generic

scsi: qla2xxx: Fix bsg_done() causing double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c2c68225b1456f4d0d393b5a8778d51bb0d5b1d0
generic

scsi: qla2xxx: Fix bsg_done() causing double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/871f6236da96c4a9712b8a29d7f555f767a47e95
generic

scsi: qla2xxx: Fix bsg_done() causing double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/74e7458537cd9349cf019862e51491f670871707
generic

scsi: qla2xxx: Fix bsg_done() causing double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/708003e1bc857dd014d4c44278d7d77c26f91b1c
generic

scsi: qla2xxx: Fix bsg_done() causing double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31f33b856d2324d86bcaef295f4d210477a1c018
generic

scsi: qla2xxx: Fix bsg_done() causing double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/27ac9679c43a09e54e2d9aae9980ada045b428e0
generic

scsi: qla2xxx: Fix bsg_done() causing double free - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/057a5bdc481e58ab853117254867ffb22caf9f6e

Patch Availability(13)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatkernel-0:5.14.0-284.172.1.el9_22026-05-26redhat
redhatkernel-rt-0:5.14.0-284.172.1.rt14.457.el9_22026-05-20redhat
redhatkernel-0:5.14.0-427.124.1.el9_42026-05-06redhat
redhatkernel-0:4.18.0-305.190.1.el8_42026-05-06redhat
redhatkernel-0:4.18.0-372.190.1.el8_62026-05-05redhat
redhatkernel-rt-0:3.10.0-1160.148.1.rt56.1300.el72026-04-27redhat
redhatkernel-0:3.10.0-1160.148.1.el72026-04-22redhat
redhatkernel-0:6.12.0-55.68.1.el10_02026-04-15redhat
redhatkernel-0:4.18.0-477.135.1.el8_82026-04-08redhat
redhatkernel-rt-0:4.18.0-553.117.1.rt7.458.el8_102026-04-06redhat
redhatkernel-0:4.18.0-553.117.1.el8_102026-04-06redhat
redhatkernel-0:6.12.0-124.47.1.el10_12026-03-30redhat
linuxKernel @ 5.10.251osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 5.10.92-2 (49 versions)5.10.251-1
linux-6.16.1.106-3~deb11u1 ... 6.1.162-1~deb11u1 (15 versions)6.1.164-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (47 versions)6.1.164-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.74-2~bpo12+1 (15 versions)6.12.74-2
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 6.18~rc7-1~exp1 (102 versions)6.18.13-1

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(12)

Data Freshness Timeline

(refreshed 7× in last 7d / 24× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 152 total refreshes for this CVE.

  1. 2026-09-18 19:27 UTCEPSS rescore
  2. 2026-09-17 19:30 UTCEPSS rescore
  3. 2026-09-16 14:07 UTCEPSS rescore
  4. 2026-09-16 05:14 UTCEPSS rescore
  5. 2026-09-15 03:10 UTCEPSS rescore
  6. 2026-09-13 16:46 UTCEPSS rescore
  7. 2026-09-12 15:00 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-11 09:36 UTCEPSS rescore
  10. 2026-09-10 09:34 UTCEPSS rescore
  11. 2026-09-08 22:00 UTCEPSS rescore
  12. 2026-09-07 16:00 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:11 UTCEPSS rescore
  16. 2026-09-01 13:53 UTCEPSS rescore
  17. 2026-08-31 16:04 UTCOSV refresh
  18. 2026-08-30 01:21 UTCEPSS rescore
  19. 2026-08-28 21:40 UTCEPSS rescore
  20. 2026-08-26 14:45 UTCEPSS rescore
  21. 2026-08-24 14:16 UTCEPSS rescore
  22. 2026-08-23 00:18 UTCEPSS rescore
  23. 2026-08-21 23:48 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-19 17:03 UTCEPSS rescore
Show 75 more
  1. 2026-08-18 13:48 UTCEPSS rescore
  2. 2026-08-16 14:55 UTCEPSS rescore
  3. 2026-08-16 02:14 UTCEPSS rescore
  4. 2026-08-15 01:30 UTCEPSS rescore
  5. 2026-08-14 20:57 UTCVendor advisory
  6. 2026-08-14 20:57 UTCGHSA enrichment
  7. 2026-08-14 08:37 UTCEG score recompute
  8. 2026-08-14 08:37 UTCVendor advisory
  9. 2026-08-14 08:37 UTCGHSA enrichment
  10. 2026-08-13 22:00 UTCEPSS rescore
  11. 2026-08-13 00:25 UTCEG score recompute
  12. 2026-08-13 00:25 UTCVendor advisory
  13. 2026-08-13 00:25 UTCGHSA enrichment
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 23:18 UTCEG score recompute
  16. 2026-08-11 23:18 UTCVendor advisory
  17. 2026-08-11 23:18 UTCGHSA enrichment
  18. 2026-08-11 13:42 UTCEPSS rescore
  19. 2026-08-11 05:52 UTCEG score recompute
  20. 2026-08-11 05:52 UTCVendor advisory
  21. 2026-08-11 05:52 UTCGHSA enrichment
  22. 2026-08-10 23:59 UTCEPSS rescore
  23. 2026-08-10 07:57 UTCVendor advisory
  24. 2026-08-10 07:57 UTCGHSA enrichment
  25. 2026-08-09 19:16 UTCEG score recompute
  26. 2026-08-09 19:16 UTCVendor advisory
  27. 2026-08-09 19:16 UTCGHSA enrichment
  28. 2026-08-09 13:46 UTCEPSS rescore
  29. 2026-08-09 08:14 UTCEG score recompute
  30. 2026-08-09 08:14 UTCVendor advisory
  31. 2026-08-09 08:14 UTCGHSA enrichment
  32. 2026-08-08 16:36 UTCEPSS rescore
  33. 2026-08-08 07:08 UTCVendor advisory
  34. 2026-08-08 07:08 UTCGHSA enrichment
  35. 2026-08-07 20:07 UTCEG score recompute
  36. 2026-08-07 20:07 UTCVendor advisory
  37. 2026-08-07 20:07 UTCGHSA enrichment
  38. 2026-08-07 16:27 UTCEPSS rescore
  39. 2026-08-06 13:46 UTCEPSS rescore
  40. 2026-08-06 02:42 UTCEG score recompute
  41. 2026-08-06 02:42 UTCVendor advisory
  42. 2026-08-06 02:42 UTCGHSA enrichment
  43. 2026-08-05 19:17 UTCEPSS rescore
  44. 2026-08-04 10:37 UTCEPSS rescore
  45. 2026-08-04 04:11 UTCEG score recompute
  46. 2026-08-04 04:11 UTCVendor advisory
  47. 2026-08-04 04:11 UTCGHSA enrichment
  48. 2026-08-03 10:35 UTCEPSS rescore
  49. 2026-08-02 19:01 UTCEG score recompute
  50. 2026-08-02 19:01 UTCVendor advisory
  51. 2026-08-02 19:01 UTCGHSA enrichment
  52. 2026-08-02 02:26 UTCEPSS rescore
  53. 2026-08-01 04:15 UTCEPSS rescore
  54. 2026-07-30 16:27 UTCEPSS rescore
  55. 2026-07-30 01:30 UTCEPSS rescore
  56. 2026-07-27 14:13 UTCEPSS rescore
  57. 2026-07-26 14:54 UTCEPSS rescore
  58. 2026-07-26 14:54 UTCEPSS rescore
  59. 2026-07-25 14:17 UTCEPSS rescore
  60. 2026-07-25 14:17 UTCEPSS rescore
  61. 2026-07-24 14:17 UTCEPSS rescore
  62. 2026-07-23 14:18 UTCEPSS rescore
  63. 2026-07-23 14:18 UTCEPSS rescore
  64. 2026-07-23 03:03 UTCEG score recompute
  65. 2026-07-22 14:08 UTCEPSS rescore
  66. 2026-07-21 15:24 UTCEPSS rescore
  67. 2026-07-20 17:08 UTCEPSS rescore
  68. 2026-07-20 13:34 UTCOSV refresh
  69. 2026-07-19 14:30 UTCEPSS rescore
  70. 2026-07-19 14:30 UTCEPSS rescore
  71. 2026-07-19 02:28 UTCEPSS rescore
  72. 2026-07-19 02:28 UTCEPSS rescore
  73. 2026-07-18 10:04 UTCEPSS rescore
  74. 2026-07-18 10:04 UTCEPSS rescore
  75. 2026-07-16 17:02 UTCEPSS rescore

Frequently asked(5)

What is CVE-2025-71238?
CVE-2025-71238 is a high vulnerability published on March 4, 2026. 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…
When was CVE-2025-71238 disclosed?
CVE-2025-71238 was first published in the National Vulnerability Database on March 4, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2025-71238 actively exploited?
CVE-2025-71238 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 90.6% of all scored CVEs.
What is the CVSS score of CVE-2025-71238?
CVE-2025-71238 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2025-71238?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2025-71238, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-71238

Explore →

Is Your Infrastructure Affected by CVE-2025-71238?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.