drbd: Potential Silent Data Corruption
Summary
GSD-2022-1002367: drbd: fix potential silent data corruption. Affects Kernel versions < 92c60ae6f827cf41604eafccbc8608ce4fb41cc1. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
The drbd package is a distributed replicated block device driver for Linux. It allows multiple servers to share the same storage device, providing high availability and data redundancy. The package is commonly used in clustered environments to ensure data integrity and fault tolerance. However, a potential vulnerability has been discovered in the drbd package that could lead to silent data corruption.
Vulnerability Detail
The vulnerability in the drbd package could result in silent data corruption. Although the impact and attack plausibility have not been proven, it is crucial to address this issue to prevent any potential data integrity issues. The vulnerability has been fixed in Linux Kernel version v4.19.238 by commit 92c60ae6f827cf41604eafccbc8608ce4fb41cc1.
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 →
Conclusion
The drbd package has been found to have a potential vulnerability that could result in silent data corruption. It is crucial to update the Linux Kernel to version v4.19.238 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The drbd package is a distributed replicated block device driver for Linux, commonly used in clustered environments to provide high availability and data redundancy.
Silent data corruption refers to the situation where data gets corrupted without any indication or error message. It can lead to data integrity issues and potential data loss.
The actual impact and attack plausibility of the vulnerability have not been proven. However, it is important to address the issue proactively to prevent any potential data corruption.
To update the Linux Kernel, fetch the latest kernel source code from the official Linux Kernel repository and apply the required commit. Follow the standard procedures for building and installing the new kernel version.
No specific workaround has been mentioned for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
