Use After Free Vulnerability in drbd Package

Kernel Updated 02 Oct 2025

Summary

24/04/2022
N/A
No i
Unrated
Not published

GSD-2022-1001012: drbd: Fix five use after free bugs in get_initial_state. Affects Kernel versions >= a29728463b254ce81ecefdf20c1a02e01d9361da, < 226e993c39405292781bfcf4b039a8db56aab362. 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 drbd package is a distributed replicated block device driver for Linux. It allows users to create networked storage devices that are synchronized across multiple nodes. The package is commonly used in high availability setups and provides data replication and failover capabilities. However, a use after free vulnerability has been discovered in the get_initial_state function of the drbd package.

Vulnerability Detail

The use after free vulnerability in the get_initial_state function of the drbd package can be exploited by an attacker to execute arbitrary code or cause a denial of service. The vulnerability occurs when the function improperly handles certain memory deallocation, leading to a situation where a pointer to freed memory is still accessible. By manipulating this pointer, an attacker can control the execution flow of the program and potentially execute malicious code. This vulnerability was introduced in version 4.5 of the Linux Kernel and has been fixed in version 5.17.3.

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

If updating the Linux Kernel is not immediately feasible, a possible workaround is to disable or restrict access to the affected functionality. This can be done by modifying the system configuration or applying specific kernel parameters. However, it is important to note that workarounds may not provide complete protection and updating to the latest kernel version is still recommended.

Conclusion

In conclusion, the use after free vulnerability in the drbd package can pose a significant security risk to systems running affected versions of the Linux Kernel. It is crucial to update the kernel to version 5.17.3 or later to mitigate this vulnerability. Workarounds may provide temporary protection, but they are not a substitute for updating to the latest kernel version. For further assistance and support, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The use after free vulnerability in the drbd package can allow an attacker to execute arbitrary code or cause a denial of service. This can lead to unauthorized access, data loss, or system instability.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file and the tool will analyze it for any known vulnerabilities.

At the time of this report, there is no known public exploit for this vulnerability. However, it is important to apply the recommended fix as soon as possible to prevent any potential exploitation.

The recommended mitigation for this vulnerability is to update the Linux Kernel to version 5.17.3 or later. Applying specific kernel parameters or disabling the affected functionality can also provide temporary mitigations, but updating the kernel is the most effective solution.

For more information about this vulnerability, you can refer to the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and the associated commit history. Additionally, you can reach out to info@devnack.com for further support on vulnerability remediation.

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