Vulnerability in riscv Kernel: Flush current cpu icache before other cpus
Summary
GSD-2021-1001698: riscv: Flush current cpu icache before other cpus. Affects Kernel versions >= fab957c11efe2f405e08b9f0d080524bc2631428, < f1c7aa87c423e765e3862349c2f095fdfccdd9b3. 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 riscv Kernel is a component of the Linux operating system that provides support for the RISC-V architecture. It is responsible for managing the core functionalities of the system, including process scheduling, memory management, and device drivers. The vulnerability in question arises from a failure to flush the current CPU's instruction cache before other CPUs, potentially leading to security issues.
Vulnerability Detail
The vulnerability in the riscv Kernel allows an attacker to exploit the lack of flushing the current CPU's instruction cache before other CPUs. This can result in unauthorized access to sensitive information or the execution of malicious code. The vulnerability was introduced in version v4.15 of the Linux Kernel and has been fixed in version v5.14.12. The impact and attack plausibility of this vulnerability have not been proven yet.
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
There is no specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the riscv Kernel, which fails to flush the current CPU's instruction cache before other CPUs, can potentially lead to unauthorized access or code execution. It is crucial to update the Linux Kernel to version v5.14.12 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially lead to unauthorized access to sensitive information or the execution of malicious code.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. It requires only a manifest file like package-lock.json to analyze and monitor for open-source vulnerabilities in real-time.
Yes, the vulnerability has been fixed in version v5.14.12 of the Linux Kernel. It is recommended to update to this version or later to address the issue.
There are no known exploits for this vulnerability at the moment. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
You can find more information about this vulnerability in the GSD-2021-1001698 JSON file available on the GitHub repository of the Cloud Security Alliance's GSD Database (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
