Open Source Vulnerability in Kernel: coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer()
Summary
GSD-2021-1001350: coresight: tmc-etf: Fix global-out-of-bounds in tmc_update_etf_buffer(). Affects Kernel versions >= 0c3fc4d5fa26092853278145aca9b21fa52a3e93, < ef0a06acc6b16388640ad367eedfa2a17f1945db. 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 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 overall stability and security of the system. The coresight module within the Kernel is responsible for tracing and debugging capabilities on ARM-based systems. One specific component of coresight, tmc-etf, handles the Embedded Trace Macrocell (ETM) buffer. This buffer is used for storing trace data during debugging and analysis processes. However, a vulnerability has been identified in the tmc_update_etf_buffer() function, which can lead to a global-out-of-bounds issue.
Vulnerability Detail
The global-out-of-bounds vulnerability in tmc_update_etf_buffer() allows an attacker to access memory outside the boundaries of the allocated buffer. By exploiting this vulnerability, an attacker may be able to read sensitive information from kernel memory or modify critical data structures, potentially leading to privilege escalation or system instability. The vulnerability was introduced in version v4.14 of the Linux Kernel and was fixed in version v5.4.133. 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 apply the patch manually to their existing Kernel version. The patch can be obtained from the commit ef0a06acc6b16388640ad367eedfa2a17f1945db in the Linux Kernel repository. By applying the patch, the global-out-of-bounds vulnerability in tmc_update_etf_buffer() will be resolved. Here is an example of how to apply the patch using the git command:
$ git apply -v ef0a06acc6b16388640ad367eedfa2a17f1945db.patch
It is important to note that applying patches manually can be error-prone and may introduce other issues. Therefore, it is recommended to update the Kernel to the latest stable version whenever possible.
Conclusion
The global-out-of-bounds vulnerability in tmc_update_etf_buffer() within the Kernel can have serious security implications. It is crucial to update the Kernel to version v5.4.133 or later to mitigate the risk. Applying the provided patch manually is also an option, but it is recommended to update to the latest stable version whenever possible. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can vary depending on the attacker's capabilities and intentions. It could potentially lead to unauthorized access to sensitive information, privilege escalation, or system instability.
You can use tools like Vulert (https://vulert.com) 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.
At the time of this report, there is no known exploit for this vulnerability. However, it is always recommended to apply security updates and patches to mitigate potential risks.
While updating the Kernel is the recommended approach, you can apply the provided patch manually to mitigate the risk. However, manual patching can be error-prone and may introduce other issues. It is best to update to the latest stable version whenever possible.
You can find more information about this vulnerability in the Linux Kernel repository. The commit ef0a06acc6b16388640ad367eedfa2a17f1945db specifically addresses this issue.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
