Vulnerability in dm era: commit metadata in postsuspend after worker stops
Summary
GSD-2022-1004749: dm era: commit metadata in postsuspend after worker stops. Affects Kernel versions >= eec40579d84873dfb7021eb24c50360f073237c5, < 1f350f3cf0c135c479a79899ee96c1cda8b669bd. 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 dm era package is a component of the Linux Kernel ecosystem. It provides support for device-mapper era target, which allows for efficient tracking of write patterns on block devices. This vulnerability affects the package's postsuspend functionality when committing metadata after the worker stops.
Vulnerability Detail
The vulnerability arises from a flaw in the dm era package's handling of commit metadata in postsuspend after the worker stops. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service attack. The vulnerability was introduced in version v3.15 of the Linux Kernel and has been fixed in version v5.4.202.
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
No specific workaround has been provided for this vulnerability.
Conclusion
In conclusion, the dm era package in the Linux Kernel is vulnerable to a flaw in its postsuspend functionality related to committing metadata after the worker stops. This vulnerability can be mitigated by updating to version v5.4.202 or later of the Linux Kernel. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability could potentially allow an attacker to execute arbitrary code or cause a denial-of-service attack.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your manifest file, such as package-lock.json, and Vulert will provide real-time alerts for open-source vulnerabilities.
Yes, the vulnerability has been fixed in version v5.4.202 of the Linux Kernel. It is recommended to update to this version or later to address the vulnerability.
No specific workarounds have been provided for this vulnerability.
You can find more information about this vulnerability in the vulnerability database maintained by the Cloud Security Alliance. The specific vulnerability ID is GSD-2022-1004749.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
