CVE-2023-53696: scsi: qla2xxx: Fix memory leak in qla2x00_probe_one()
In the Linux kernel, the following vulnerability has been resolved:
scsi: qla2xxx: Fix memory leak in qla2x00_probe_one()
There is a memory leak reported by kmemleak:
unreferenced object 0xffffc900003f0000 (size 12288):
comm "modprobe", pid 19117, jiffies 4299751452 (age 42490.264s)
hex dump (first 32 bytes):
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
backtrace:
[<00000000629261a8>] __vmalloc_node_range+0xe56/0x1110
[<0000000001906886>] __vmalloc_node+0xbd/0x150
[<000000005bb4dc34>] vmalloc+0x25/0x30
[<00000000a2dc1194>] qla2x00_create_host+0x7a0/0xe30 [qla2xxx]
[<0000000062b14b47>] qla2x00_probe_one+0x2eb8/0xd160 [qla2xxx]
[<00000000641ccc04>] local_pci_probe+0xeb/0x1a0
The root cause is traced to an error-handling path in qla2x00_probe_one()
when the adapter "base_vha" initialize failed. The fab_scan_rp "scan.l" is
used to record the port information and it is allocated in
qla2x00_create_host(). However, it is not released in the error handling
path "probe_failed".
Fix this by freeing the memory of "scan.l" when an error occurs in the
adapter initialization process.
Security readout for executives and security teams
Plain-English summary
CVE-2023-53696 is a Linux kernel memory leak in the qla2xxx SCSI driver. It occurs during adapter probing when initialization fails, leaving allocated scan data unreleased. The source does not provide CVSS, public exploitation evidence, or business-impact detail.
Executive priority
Treat as routine kernel hygiene unless qla2xxx-equipped storage hosts are critical or unstable. No source provided evidence of active exploitation or remote compromise.
Technical view
The bug is in qla2x00_probe_one(). scan.l is allocated by qla2x00_create_host() for fab_scan_rp port information, but the probe_failed error path did not free it when base_vha initialization failed. Stable kernel commits add cleanup for that failure path.
Likely exposure
Exposure appears limited to Linux systems using the qla2xxx driver, commonly associated with QLogic Fibre Channel adapters. Confirm actual exposure through kernel version, driver presence, and hardware inventory.
Exploitation context
The bundle shows KEV is false and provides no evidence of active exploitation. The described condition is an initialization failure path, not a documented remote attack path.
Researcher notes
The record lacks CVSS, CWE, and detailed distro mapping. Analysis should focus on confirming backports and reproducing only the benign allocation cleanup condition in a controlled lab.
Mitigation direction
Review vendor or distribution kernel advisories for backported fixes.
Update to a kernel containing the referenced stable commits.
Prioritize systems with qla2xxx hardware or loaded driver modules.
If updates are delayed, monitor affected hosts for unusual kernel memory pressure.
Validation and detection
Identify Linux hosts running affected kernel versions listed in the CVE bundle.
Check whether the qla2xxx driver is present or loaded.
Confirm vendor kernel changelogs include the qla2xxx memory leak fix.
Review kernel logs and memory telemetry for repeated probe failures.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2023-53696 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
5Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
Oct 22, 2025, 13:23 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.