Memory Leak Vulnerability in virtio-blk Package

Kernel Updated 02 Oct 2025

Summary

03/08/2021

Disclosed on

N/A

Severity

No i

Fix available

Unrated

Severity

Not published

CVSS Score

GSD-2021-1001186: virtio-blk: Fix memory leak among suspend/resume procedure. Affects Kernel versions < 29a2f4a3214aa14d61cc9737c9f886dae9dbb710. 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 Browse

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.

Background

The virtio-blk package is a component of the Linux Kernel ecosystem. It provides a virtual block device driver for the VirtIO framework, allowing virtual machines to access block devices efficiently. This package is widely used in virtualization environments and is critical for the proper functioning of virtual machines.

Vulnerability Detail

The identified vulnerability in the virtio-blk package relates to a memory leak issue during the suspend/resume procedure. When a virtual machine is suspended and then resumed, the package fails to release certain memory resources, leading to a gradual accumulation of memory over time. This can result in memory exhaustion, degraded performance, and potential denial-of-service conditions. The vulnerability has been assigned the ID GSD-2021-1001186 and has been fixed in Linux Kernel version v5.13.4 by commit 29a2f4a3214aa14d61cc9737c9f886dae9dbb710.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.13.4 or later. This can be done by obtaining the updated kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it for the target system. Alternatively, users can wait for their Linux distribution to provide an updated package containing the fixed version of the kernel.

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 available for this vulnerability. It is essential to apply the fix by updating the Linux Kernel to the recommended version.

Conclusion

The memory leak vulnerability in the virtio-blk package can have severe consequences in virtualization environments. It is crucial to update the Linux Kernel to version v5.13.4 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

FAQ

What is the impact of this vulnerability?

The vulnerability can lead to memory exhaustion, degraded performance, and potential denial-of-service conditions in virtualization environments utilizing the virtio-blk package.

How can I check if my system is affected?

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It requires no signup and uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.