CVE-2026-97532Hinoki check available

Kernel crash via qla2xxx allocation cleanup

Published Sep 25, 2026 · Updated Sep 25, 2026

Double-free handling in Linux before 6.18.53 and 7.2.7 crashes the kernel when qla2xxx adapter allocation fails during probe. Error labels in qla2x00_mem_alloc() free adapter members without clearing their pointers, after which qla2x00_mem_free() frees them again and can pass a NULL DMA pool to dma_pool_free(). Reachability requires a qla2xxx adapter and an allocation failure during probing; the published record establishes a kernel crash but no attacker-controlled trigger.

CVSS severityUnavailable
Unscored
EPSS probability0.20%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Double-free handling in Linux before 6.18.53 and 7.2.7 crashes the kernel when qla2xxx adapter allocation fails during probe. Error labels in qla2x00_mem_alloc() free adapter members without clearing their pointers, after which qla2x00_mem_free() frees them again and can pass a NULL DMA pool to dma_pool_free(). Reachability requires a qla2xxx adapter and an allocation failure during probing; the published record establishes a kernel crash but no attacker-controlled trigger.

The record

CVE
CVE-2026-97532
Published
Sep 25, 2026
Updated
Sep 25, 2026
Vendor
The Linux Kernel Organization
Product
Linux
Classifications
T1499
Attack vector
Unavailable
Privileges
Unavailable

Timeline

How it unfolded

  1. Sep 25, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 25, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <6.18.53
  2. Affected versionversion=0 <7.2.7
  3. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <286d9594a022dd7e0caa3de9daa63b896bc70d43
  4. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d90f0feb929f6c0f3010f9af4747c7230b75993
  5. Affected versionversion=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a57570229edb7a0990d5c8067daeb9ac8858a961

What conditions does exploitation require?

Attack vectorUnavailable in this record.
Required privilegesUnavailable in this record.

What is affected?

The Linux Kernel Organization · Linuxversion=0 <6.18.53; version=0 <7.2.7; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <286d9594a022dd7e0caa3de9daa63b896bc70d43; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <6d90f0feb929f6c0f3010f9af4747c7230b75993; version=1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 <a57570229edb7a0990d5c8067daeb9ac8858a961

Published CVSS scores

No CVSS assessment is available in this record.

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
VectorUnavailable
PrivilegesUnavailable
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1499Endpoint Denial of Service

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started