Vulnerability in coresight: cpu-debug Package
Summary
GSD-2022-1003541: coresight: cpu-debug: Replace mutex with mutex_trylock on panic notifier. Affects Kernel versions >= 2227b7c7463402ce92706a6f35c82cad6e8ee19a, < 96414e2cdc2840752a14bfca995578cccbaf2761. 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 coresight: cpu-debug package is a component of the Linux Kernel, which is responsible for providing debugging capabilities for CPUs. It allows developers to monitor and analyze the behavior of CPUs during runtime. The package includes various features and functionalities to facilitate debugging processes. However, a vulnerability has been discovered in the package that could potentially be exploited by attackers.
Vulnerability Detail
The vulnerability in the coresight: cpu-debug package involves the use of a mutex instead of mutex_trylock on the panic notifier. This vulnerability was introduced in version v4.13 of the Linux Kernel and was fixed in version v5.10.122. The impact and attack plausibility of this vulnerability have not been proven yet. However, if exploited, it could lead to unauthorized access or denial of service. The specific technical details of the vulnerability can be found in the provided references.
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 manually replace the mutex with mutex_trylock on the panic notifier in the affected code. Here is an example of how the code can be modified:
// Original code
mutex_lock(&panic_mutex);
// Modified code
if (mutex_trylock(&panic_mutex)) {
// Code execution when mutex_trylock succeeds
} else {
// Code execution when mutex_trylock fails
}
Conclusion
In conclusion, the coresight: cpu-debug package in the Linux Kernel is vulnerable to a mutex-related issue. It is recommended to update the kernel to the latest version to mitigate this vulnerability. If immediate update is not possible, the provided workaround can be implemented. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The coresight: cpu-debug package is a component of the Linux Kernel that provides debugging capabilities for CPUs.
The impact of this vulnerability is not yet proven, but if exploited, it could lead to unauthorized access or denial of service.
To fix this vulnerability, update the Linux Kernel to version v5.10.122 or later.
Yes, a possible workaround is to manually replace the mutex with mutex_trylock on the panic notifier in the affected code.
More information about this vulnerability can be found in the provided references.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
