Fix resource leak in case of probe failure in scsi: megaraid_sas

Kernel Updated 02 Oct 2025

Summary

03/08/2021
N/A
No i
Unrated
Not published

GSD-2021-1001275: scsi: megaraid_sas: Fix resource leak in case of probe failure. Affects Kernel versions < 0680db6f41920b2c91c7df3cc9cd5968701a6f74. 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 scsi: megaraid_sas package is a SCSI driver for the MegaRAID SAS family of RAID controllers. It provides support for managing and controlling SCSI devices connected to these controllers. The package is a part of the Linux Kernel ecosystem.

Vulnerability Detail

The vulnerability in scsi: megaraid_sas occurs in the case of probe failure. It leads to a resource leak, which can have various consequences. A resource leak can result in memory leaks, file descriptor leaks, or other types of resource leaks, causing performance degradation or denial of service. The vulnerability has been identified and fixed in the Linux Kernel version v5.10.52 by commit 0680db6f41920b2c91c7df3cc9cd5968701a6f74.

How To Fix

No fixed version is published for this vulnerability.

To fix the vulnerability, it is recommended to update the scsi: megaraid_sas package to the fixed version v5.10.52 or later. This can be done by updating the Linux Kernel to the corresponding version. The fix ensures that the resource leak is properly handled in case of probe failure, preventing any potential issues.

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

Conclusion

The vulnerability in scsi: megaraid_sas, which caused a resource leak in case of probe failure, has been fixed in the Linux Kernel version v5.10.52. It is recommended to update the package to the fixed version to ensure the proper handling of resource leaks. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

scsi: megaraid_sas is a SCSI driver for the MegaRAID SAS family of RAID controllers in the Linux Kernel ecosystem. It provides support for managing and controlling SCSI devices connected to these controllers.

The resource leak in scsi: megaraid_sas can lead to memory leaks, file descriptor leaks, or other types of resource leaks. This can result in performance degradation or denial of service.

To fix the vulnerability, update the scsi: megaraid_sas package to the fixed version v5.10.52 or later by updating the Linux Kernel.

No specific workaround has been mentioned for this vulnerability. It is recommended to update to the fixed version.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix the vulnerability, it is recommended to update the scsi: megaraid_sas package to the fixed version v5.10.52 or later. This can be done by updating the Linux Kernel to the corresponding version. The fix ensures that the resource leak is properly handled in case of probe failure, preventing any potential issues.

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

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.