Memory Leak in nvme-loop: Fix in Linux Kernel

Kernel Updated 02 Oct 2025

Summary

31/05/2021
N/A
No i
Unrated
Not published

GSD-2021-1000497: nvme-loop: fix memory leak in nvme_loop_create_ctrl(). Affects Kernel versions >= 3a85a5de29ea779634ddfd768059e06196687aba, < 551ba08d4b7eb26f75758cdb9f15105b276517ad. 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 nvme-loop is a component in the Linux Kernel that provides support for NVMe over Fabrics (NVMe-oF) loopback devices. It allows users to create virtual NVMe devices that are backed by regular files or block devices. These virtual devices can then be accessed as if they were real NVMe devices. The nvme-loop component has been vulnerable to a memory leak issue.

Vulnerability Detail

The vulnerability in nvme-loop is a memory leak that occurs in the nvme_loop_create_ctrl() function. This function is responsible for creating and initializing the NVMe controller for the loop device. However, due to a coding error, memory allocated during the creation of the controller is not properly freed, leading to a memory leak. This vulnerability can be exploited by an attacker to exhaust system memory resources, potentially causing a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven.

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 nvme-loop component in the Linux Kernel has been found to have a memory leak vulnerability. This vulnerability has been fixed in Linux Kernel version v5.12.7. Users are advised to update their Linux Kernel to at least this version to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

nvme-loop is a component in the Linux Kernel that provides support for NVMe over Fabrics (NVMe-oF) loopback devices. It allows users to create virtual NVMe devices that are backed by regular files or block devices.

The impact of this vulnerability is a potential denial-of-service condition due to memory exhaustion. However, the actual impact and attack plausibility have not been proven.

To fix this vulnerability, users should update their Linux Kernel to at least version v5.12.7, where the memory leak issue has been fixed.

No specific workaround has been mentioned for this vulnerability.

Users can obtain the updated Linux Kernel from the official Linux Kernel repository: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/

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