Vulnerability in Kernel: nbd_cleanup() Function

Kernel Updated 02 Oct 2025

Summary

28/06/2022
N/A
No i
Unrated
Not published

GSD-2022-1002530: nbd: call genl_unregister_family() first in nbd_cleanup(). Affects Kernel versions < 3d5da1ffba3388c2ae2e6c598855a4d887d3bf79. 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 Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It manages system resources, facilitates communication between software and hardware, and ensures the stability and security of the system. The nbd (Network Block Device) is a kernel module that allows remote storage devices to be accessed over a network. It provides a virtual block device interface for network-based storage access. The nbd_cleanup() function is responsible for cleaning up resources and unregistering the nbd module. However, a vulnerability has been identified in the nbd_cleanup() function, which could potentially lead to security issues.

Vulnerability Detail

The vulnerability in the nbd_cleanup() function arises from the improper order of operations during cleanup. Specifically, the genl_unregister_family() function, which unregisters the nbd module from the Generic Netlink subsystem, is not called before other cleanup operations. This can result in the nbd module not being properly unregistered, potentially leaving the system vulnerable to attacks or resource leaks. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in the Linux Kernel version v5.18.4 by commit 3d5da1ffba3388c2ae2e6c598855a4d887d3bf79.

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

As this vulnerability has been fixed in the Linux Kernel version v5.18.4, there is no specific workaround available. It is recommended to update the Kernel to the fixed version as soon as possible.

Conclusion

The vulnerability in the nbd_cleanup() function of the Kernel has the potential to introduce security issues or resource leaks in systems running an affected version. It is crucial to update the Linux Kernel to version v5.18.4 or later to mitigate this vulnerability. By following the recommended steps for fixing the vulnerability, users can ensure the security and stability of their systems. For additional support and guidance, feel free to contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The impact of this vulnerability is not yet proven. However, if exploited, it could potentially lead to security issues or resource leaks in systems running an affected version of the Linux Kernel.

You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it to identify any open-source vulnerabilities, including this one.

The exact attack vector and exploitability of this vulnerability have not been proven yet. However, as it affects the Kernel, which is a critical component of the operating system, it is advisable to apply the fix as soon as possible to mitigate any potential risks.

There are no known instances of this vulnerability being exploited in the wild. However, it is always recommended to stay updated with the latest security patches and fixes to minimize the risk of exploitation.

For further support and assistance in remediating this vulnerability, you can reach out to info@devnack.com. Our team of experts will be happy to assist you in securing your systems.

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