Vulnerability in Kernel: Put LLD module refcnt after SCSI device is released

Kernel Updated 02 Oct 2025

Summary

14/11/2021
N/A
No i
Unrated
Not published

GSD-2021-1001967: scsi: core: Put LLD module refcnt after SCSI device is released. Affects Kernel versions < 61a0faa89f21861d1f8d059123b5c285a5d9ffee. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It manages the communication between software and hardware, including handling input/output operations. The SCSI (Small Computer System Interface) subsystem is responsible for managing SCSI devices, such as hard drives and tape drives, connected to the system. The LLD (Low-Level Driver) module is a component of the SCSI subsystem that provides the necessary functionality to interact with specific SCSI devices. This vulnerability in the Kernel's SCSI core affects the handling of the LLD module reference count after a SCSI device is released.

Vulnerability Detail

The vulnerability arises from a flaw in the SCSI core of the Kernel, where the LLD module reference count is not properly managed after a SCSI device is released. This can lead to a use-after-free condition, where the Kernel may attempt to access the LLD module after it has been freed from memory. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. 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. Users are advised to update their Kernel to the fixed version as soon as possible.

Conclusion

The vulnerability in the Kernel's SCSI core, which improperly manages the LLD module reference count after a SCSI device is released, has been addressed in the latest version of the Linux Kernel. Users are advised to update their Kernel to the fixed version to mitigate the risk of exploitation. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices.

The SCSI subsystem is responsible for managing SCSI devices, such as hard drives and tape drives, connected to the system.

The LLD (Low-Level Driver) module is a component of the SCSI subsystem that provides the necessary functionality to interact with specific SCSI devices.

A use-after-free vulnerability occurs when a program attempts to access memory that has already been freed. This can lead to crashes, data corruption, or the execution of arbitrary code.

An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition.

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