Vulnerability in Kernel: riscv: Fix config KASAN && DEBUG_VIRTUAL
Summary
GSD-2022-1000841: riscv: Fix config KASAN && DEBUG_VIRTUAL. Affects Kernel versions >= 8ad8b72721d0f07fa02dbe71f901743f9c71c8e6, < dd9dd24fd7cb5310fa1db2b1b03431c96663fa7c. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and acts as an interface between hardware and software. It manages system resources, facilitates communication between different software components, and ensures the security and stability of the system. The riscv architecture is a popular open-source instruction set architecture used in various devices. This vulnerability specifically affects the riscv configuration with KASAN (Kernel Address Sanitizer) and DEBUG_VIRTUAL enabled.
Vulnerability Detail
The vulnerability arises due to a misconfiguration in the riscv architecture when both KASAN and DEBUG_VIRTUAL options are enabled. It is important to note that the impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v5.6 of the Linux Kernel by commit 8ad8b72721d0f07fa02dbe71f901743f9c71c8e6 and has been fixed in version v5.10.104 by commit dd9dd24fd7cb5310fa1db2b1b03431c96663fa7c. For more detailed information, please refer to the references link.
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 Kernel affecting the riscv configuration with KASAN and DEBUG_VIRTUAL enabled has been identified and fixed in version v5.10.104. It is recommended to update the Linux Kernel to the fixed version to ensure the security and stability of the system. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is currently unknown as the attack plausibility has not been proven. However, it is always recommended to keep the software up to date to mitigate potential security risks.
You can use Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.
No known exploit for this vulnerability has been reported at the moment.
The recommended solution is to update the Linux Kernel to the fixed version. However, if updating is not feasible, you can consider disabling the KASAN and DEBUG_VIRTUAL options in the riscv configuration. Keep in mind that this may affect other functionalities and should be done with caution.
You can find more information about this vulnerability in the provided references link.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
