Vulnerability in Kernel: tee: amdtee: fix an IS_ERR() vs NULL bug
Summary
GSD-2021-1002696: tee: amdtee: fix an IS_ERR() vs NULL bug. Affects Kernel versions >= 757cc3e9ff1d72d014096399d6e2bf03974d9da1, < 640e28d618e82be78fb43b4bf5113bc90d6aa442. 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 fundamental 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 tee (Trusted Execution Environment) subsystem in the Kernel enables secure execution of code in isolated environments. The amdtee module specifically provides support for AMD TrustZone-based TEEs. However, a vulnerability has been identified in the amdtee module that involves an IS_ERR() vs NULL bug.
Vulnerability Detail
The vulnerability in the amdtee module arises from an IS_ERR() vs NULL bug. This bug can potentially lead to security issues and system instability. The bug was introduced in version v5.6 of the Linux Kernel by commit 757cc3e9ff1d72d014096399d6e2bf03974d9da1 and has been fixed in version v5.10.88 by commit 640e28d618e82be78fb43b4bf5113bc90d6aa442. The bug occurs when the IS_ERR() macro is used incorrectly to check for errors, resulting in a NULL pointer dereference. Attackers may be able to exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition.
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 patches or backport the fix to the affected Kernel version. The specific steps for applying patches or backporting may vary depending on the system setup and the version of the Kernel in use. It is recommended to consult the official documentation and community resources for detailed instructions on applying patches or backporting fixes.
Conclusion
The vulnerability in the amdtee module of the Kernel can lead to security risks and system instability. It is crucial to update the Kernel to the fixed version to mitigate these risks. Applying patches or backporting the fix can serve as a temporary workaround. Tools like Vulert can be used to check if your system is affected by this vulnerability. For further support and guidance on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially allow attackers to execute arbitrary code or cause a denial-of-service condition. It is important to update the Kernel to the fixed version to mitigate the risk.
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 are no known exploits for this vulnerability. However, it is important to apply the fix as soon as possible to prevent potential exploitation.
Yes, this vulnerability can be exploited remotely if the affected system is accessible over a network. It is crucial to update the Kernel to the fixed version to mitigate the risk of remote exploitation.
For further support on vulnerability remediation and assistance with updating the Kernel, you can reach out to info@devnack.com.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
