Fix scheduling while atomic in scsi: qla2xxx

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001768: scsi: qla2xxx: Fix scheduling while atomic. Affects Kernel versions < 826a9d4a00d1424afa961504aec6298ee92d5053. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The scsi: qla2xxx is a driver in the Linux Kernel that provides support for QLogic Fibre Channel Host Bus Adapters (HBAs). These HBAs are used for connecting servers to storage devices in data centers. The qla2xxx driver handles the communication between the server and the storage device, ensuring reliable and efficient data transfer. However, a vulnerability has been discovered in the qla2xxx driver that could potentially lead to a scheduling issue while in an atomic context.

Vulnerability Detail

The vulnerability in the scsi: qla2xxx driver arises from improper scheduling while in an atomic context. Atomic context refers to a situation where the execution of code cannot be interrupted or preempted by other code. In this case, the qla2xxx driver is not properly handling atomic context, which could result in a race condition or deadlock. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition or execute arbitrary code with elevated privileges. 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 specific workaround mentioned for this vulnerability.

Conclusion

The scsi: qla2xxx driver in the Linux Kernel is vulnerable to a scheduling issue while in an atomic context. This vulnerability could potentially lead to a denial-of-service (DoS) condition or arbitrary code execution. It is recommended to update the Linux Kernel to version v5.15.33 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The scsi: qla2xxx driver is a component of the Linux Kernel that provides support for QLogic Fibre Channel Host Bus Adapters (HBAs). It enables communication between servers and storage devices in data centers.

An atomic context refers to a situation where the execution of code cannot be interrupted or preempted by other code. It ensures that certain critical operations are performed without interference.

A race condition is a situation in which the behavior of a system depends on the relative timing of events. It occurs when multiple threads or processes access shared data concurrently, leading to unpredictable outcomes.

A deadlock is a situation where two or more processes are unable to proceed because each is waiting for the other to release a resource. This can result in a system freeze or unresponsiveness.

The potential impacts of this vulnerability include denial-of-service (DoS) conditions and the execution of arbitrary code with elevated privileges. However, the actual impact and attack plausibility have not been proven yet.

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