ARM: 9170/1: fix panic when kasan and kprobe are enabled in Kernel
Summary
GSD-2022-1000622: ARM: 9170/1: fix panic when kasan and kprobe are enabled. Affects Kernel versions >= 35aa1df4328340f38edc46f00837f08d33d49f63, < ba1863be105b06e10d0e2f6b1b8a0570801cfc71. 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 crucial component of the Linux operating system that acts as a bridge between the hardware and software layers. It provides essential services and manages system resources. The vulnerability in question affects the ARM architecture and specifically impacts the interaction between the Kernel Address Sanitizer (KASAN) and Kernel Probes (Kprobes). KASAN is a dynamic memory error detector, while Kprobes allows developers to insert instrumentation code into running Kernel code. When both KASAN and Kprobes are enabled, a panic condition can occur, leading to system instability and potential security risks.
Vulnerability Detail
The vulnerability arises due to an issue in the ARM architecture code of the Kernel. When KASAN and Kprobes are simultaneously enabled, a panic condition can be triggered. This panic can result in system crashes, denial of service, or potential exploitation by malicious actors. The vulnerability was introduced in version v2.6.25 of the Linux Kernel and has been fixed in version v5.16.5. It is important to note that 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
As a workaround, users can disable either KASAN or Kprobes to prevent the panic condition. Disabling KASAN can be achieved by removing the 'kasan' kernel command-line parameter or by recompiling the Kernel without KASAN support. Similarly, disabling Kprobes can be done by removing the 'kprobes' kernel command-line parameter or by recompiling the Kernel without Kprobes support. However, it is important to note that disabling these features may impact system monitoring and debugging capabilities.
Conclusion
The ARM architecture vulnerability in the Kernel, which causes a panic condition when KASAN and Kprobes are enabled, has been addressed in version v5.16.5. Users are advised to update their Linux Kernel to this version or later to mitigate the vulnerability. Alternatively, disabling either KASAN or Kprobes can serve as a temporary workaround, although it may impact system monitoring and debugging capabilities. It is important to stay vigilant and apply the necessary fixes to prevent potential exploitation. For further support, contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to system crashes, denial of service, or potential exploitation by malicious actors.
You can use the Vulert playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time monitoring and alerts for open-source vulnerabilities, including this one.
While updating the Kernel is the recommended solution, you can mitigate the vulnerability by disabling either KASAN or Kprobes. However, this may impact system monitoring and debugging capabilities.
As of now, there are no known exploits for this vulnerability. However, it is crucial to apply the fix or workaround to prevent potential exploitation.
For further support on vulnerability remediation, you can reach out to info@devnack.com. They can provide guidance and assistance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
