CVE-2025-71235: scsi: qla2xxx: Delay module unload while fabric scan in progress
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 528b2f1027edfb52af0171f0f4b227fb356dde05, 7062eb0c488f35730334daad9495d9265c574853, 8890bf450e0b6b283f48ac619fca5ac2f14ddd62; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.126.1-1; cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0 5.15.202.1-1.
Low priority for now. Upgrade to Linux Linux 528b2f1027edfb52af0171f0f4b227fb356dde05, 7062eb0c488f35730334daad9495d9265c574853, 8890bf450e0b6b283f48ac619fca5ac2f14ddd62; azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 6.6.126.1-1; cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0 5.15.202.1-1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
In the Linux kernel, the following vulnerability has been resolved: scsi: qla2xxx: Delay module unload while fabric scan in progress System crash seen during load/unload test in a loop. [105954.384919] RBP: ffff914589838dc0 R08: 0000000000000000 R09: 0000000000000086 [105954.384920] R10: 000000000000000f R11: ffffa31240904be5 R12: ffff914605f868e0 [105954.384921] R13: ffff914605f86910 R14: 0000000000008010 R15: 00000000ddb7c000 [105954.384923] FS: 0000000000000000(0000) GS:ffff9163fec40000(0000) knlGS:0000000000000000 [105954.384925] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 [105954.384926] CR2: 000055d31ce1d6a0 CR3: 0000000119f5e001 CR4: 0000000000770ee0 [105954.384928] PKRU: 55555554 [105954.384929] Call Trace: [105954.384931] <IRQ> [105954.384934] qla24xx_sp_unmap+0x1f3/0x2a0 [qla2xxx] [105954.384962] ? qla_async_scan_sp_done+0x114/0x1f0 [qla2xxx] [105954.384980] ? qla24xx_els_ct_entry+0x4de/0x760 [qla2xxx] [105954.384999] ? __wake_up_common+0x80/0x190 [105954.385004] ? qla24xx_process_response_queue+0xc2/0xaa0 [qla2xxx] [105954.385023] ? qla24xx_msix_rsp_q+0x44/0xb0 [qla2xxx] [105954.385040] ? __handle_irq_event_percpu+0x3d/0x190 [105954.385044] ? handle_irq_event+0x58/0xb0 [105954.385046] ? handle_edge_irq+0x93/0x240 [105954.385050] ? __common_interrupt+0x41/0xa0 [105954.385055] ? common_interrupt+0x3e/0xa0 [105954.385060] ? asm_common_interrupt+0x22/0x40 The root cause of this was that there was a free (dma_free_attrs) in the interrupt context. There was a device discovery/fabric scan in progress. A module unload was issued which set the UNLOADING flag. As part of the discovery, after receiving an interrupt a work queue was scheduled (which involved a work to be queued). Since the UNLOADING flag is set, the work item was not allocated and the mapped memory had to be freed. The free occurred in interrupt context leading to system crash. Delay the driver unload until the fabric scan is complete to avoid the crash.
- Published
- Feb 18, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.1% · 3th percentile
- CWE
- CWE-362
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel4.8 and later · before 5.10.251
- linux linux kernel5.11 and later · before 5.15.201
- linux linux kernel5.16 and later · before 6.1.164
- linux linux kernel6.2 and later · before 6.6.125
- linux linux kernel6.7 and later · before 6.12.72
- linux linux kernel6.13 and later · before 6.18.11
- linux linux kernel6.19 and later · before 6.19.1
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 4.8affected
- 783e0dc4f66ade6bbd8833b6bae778158d54c1a6 and later · before d8af012f92eee021c6ebb7093e65813c926c336baffected · git
- 783e0dc4f66ade6bbd8833b6bae778158d54c1a6 and later · before 891f9969a29e9767a453cef4811c8d2472ccab49affected · git
- 783e0dc4f66ade6bbd8833b6bae778158d54c1a6 and later · before 984dc1a51bf6fc3ca4e726abe790ec38952935d8affected · git
- 783e0dc4f66ade6bbd8833b6bae778158d54c1a6 and later · before 528b2f1027edfb52af0171f0f4b227fb356dde05affected · git
- 783e0dc4f66ade6bbd8833b6bae778158d54c1a6 and later · before d70f71d4c92bcb8b6a21ac62d4ea3e87721f4f32affected · git
- 783e0dc4f66ade6bbd8833b6bae778158d54c1a6 and later · before c068ebbaf52820d6bdefb9b405a1e426663c635aaffected · git
- 783e0dc4f66ade6bbd8833b6bae778158d54c1a6 and later · before 7062eb0c488f35730334daad9495d9265c574853affected · git
- 783e0dc4f66ade6bbd8833b6bae778158d54c1a6 and later · before 8890bf450e0b6b283f48ac619fca5ac2f14ddd62affected · git
- before 4.8not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | linux | before 5.10.251-1 | 5.10.251-1 |
| Debian:12 | linux | before 6.1.164-1 | 6.1.164-1 |
| Debian:13 | linux | before 6.12.73-1 | 6.12.73-1 |
| Debian:14 | linux | before 6.18.12-1 | 6.18.12-1 |
| openSUSE:Tumbleweed | kernel-source | before 6.19.8-1.1 | 6.19.8-1.1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2025-71232Feb 18, 2026 · scsi: qla2xxx: Free sp in error path to fix system crash22Monitor
- ← EarlierCVE-2025-71234Feb 18, 2026 · wifi: rtl8xxxu: fix slab-out-of-bounds in rtl8xxxu_sta_add31Monitor
- Later →CVE-2025-71236Feb 18, 2026 · scsi: qla2xxx: Validate sp before freeing associated memory22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 528b2f1027edfb52af0171f0f4b227fb356dde05 | Vendor (CNA) |
| Linux Linux | 7062eb0c488f35730334daad9495d9265c574853 | Vendor (CNA) |
| Linux Linux | 8890bf450e0b6b283f48ac619fca5ac2f14ddd62 | Vendor (CNA) |
| Linux Linux | 891f9969a29e9767a453cef4811c8d2472ccab49 | Vendor (CNA) |
| Linux Linux | 984dc1a51bf6fc3ca4e726abe790ec38952935d8 | Vendor (CNA) |
| Linux Linux | c068ebbaf52820d6bdefb9b405a1e426663c635a | Vendor (CNA) |
| Linux Linux | d70f71d4c92bcb8b6a21ac62d4ea3e87721f4f32 | Vendor (CNA) |
| Linux Linux | d8af012f92eee021c6ebb7093e65813c926c336b | Vendor (CNA) |
| azl3 kernel 6.6.121.1-1 on Azure Linux 3.0 | 6.6.126.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| cbl2 kernel 5.15.200.1-1 on CBL Mariner 2.0 | 5.15.202.1-1 · CBL-Mariner Releases | Microsoft (MSRC) |
| debian:linux | 6.1.164-1 · Debian:12 | Package registry (OSV) |
| opensuse:kernel-source | 6.19.8-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (7 more)Show less
- git.kernel.org/stable/c/7062eb0c488f35730334daad9495d9265c574853
- git.kernel.org/stable/c/8890bf450e0b6b283f48ac619fca5ac2f14ddd62
- git.kernel.org/stable/c/891f9969a29e9767a453cef4811c8d2472ccab49
- git.kernel.org/stable/c/984dc1a51bf6fc3ca4e726abe790ec38952935d8
- git.kernel.org/stable/c/c068ebbaf52820d6bdefb9b405a1e426663c635a
- git.kernel.org/stable/c/d70f71d4c92bcb8b6a21ac62d4ea3e87721f4f32
- git.kernel.org/stable/c/d8af012f92eee021c6ebb7093e65813c926c336b
Vendor advisories and official records. Exploit/PoC links are deliberately left out.