Memory Leak in qla2xxx Driver in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

28/10/2021
N/A
No i
Unrated
Not published

UVI-2021-1001865: scsi: qla2xxx: Fix a memory leak in an error path of qla2x00_process_els(). Affects Kernel versions >= 8c0eb596baa51f2b43949c698c644727ef17805c, < a7fbb56e6c941d9f59437b96412a348e66388d3e. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The qla2xxx driver is a SCSI driver in the Linux Kernel that provides support for QLogic Fibre Channel Host Bus Adapters (HBAs). It allows communication between the operating system and Fibre Channel storage devices. The driver is responsible for handling various SCSI commands and events.

Vulnerability Detail

The qla2xxx driver in the Linux Kernel prior to version 5.14.15 suffers from a memory leak vulnerability in the error path of the qla2x00_process_els() function. This vulnerability was introduced in version 3.11 of the Linux Kernel. An attacker could exploit this vulnerability to cause a denial-of-service condition by repeatedly triggering the error path, leading to the exhaustion of system memory resources. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no known workaround for this vulnerability. It is recommended to apply the official fix by updating the Linux Kernel.

Conclusion

The memory leak vulnerability in the qla2xxx driver of the Linux Kernel can be fixed by updating to version 5.14.15 or later. It is important to apply this fix to prevent potential denial-of-service attacks. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The qla2xxx driver is a SCSI driver in the Linux Kernel that provides support for QLogic Fibre Channel Host Bus Adapters (HBAs). It allows communication between the operating system and Fibre Channel storage devices.

The vulnerability can lead to a memory leak in the qla2xxx driver, potentially causing a denial-of-service condition by exhausting system memory resources.

An attacker can exploit this vulnerability by repeatedly triggering the error path of the qla2x00_process_els() function, leading to the accumulation of memory leaks and eventual exhaustion of system memory resources.

No, there is no known workaround for this vulnerability. It is recommended to apply the official fix by updating the Linux Kernel.

You can find more information about this vulnerability in the official Linux Kernel repository and the Cloud Security Alliance's GSD database.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback