Use After Free Vulnerability in crypto: ccree
Summary
GSD-2022-1002116: crypto: ccree - Fix use after free in cc_cipher_exit(). Affects Kernel versions >= 63ee04c8b491ee148489347e7da9fbfd982ca2bb, < c93017c8d5ebf55a4e453ac7c84cc84cf92ab570. 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 crypto: ccree package is a component of the Linux Kernel, which provides cryptographic functionality. It includes the cc_cipher_exit() function, which is responsible for freeing resources used by the ccree cipher. However, a use after free vulnerability has been discovered in this function, which could lead to potential security issues.
Vulnerability Detail
The use after free vulnerability in cc_cipher_exit() occurs when the function attempts to access memory that has already been freed. This can result in a variety of issues, including crashes, memory corruption, and potential remote code execution. The vulnerability was introduced in version v4.17 of the Linux Kernel and has been fixed in version v5.10.110.
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 known workaround for this vulnerability. It is essential to update the Linux Kernel to the fixed version to mitigate the risk.
Conclusion
The use after free vulnerability in crypto: ccree's cc_cipher_exit() function can lead to severe security issues, including crashes, memory corruption, and potential remote code execution. It is crucial to update the Linux Kernel to version v5.10.110 or later to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The use after free vulnerability in cc_cipher_exit() can lead to crashes, memory corruption, and potential remote code execution. It poses a significant security risk.
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, and Vulert will provide real-time monitoring and alerts for open-source vulnerabilities.
No, there is no known workaround for this vulnerability. It is crucial to update the Linux Kernel to the fixed version.
The vulnerability was introduced in version v4.17 of the Linux Kernel. All versions between v4.17 and v5.10.110 are affected.
You can find more information about this vulnerability in the Open Source Vulnerability Database at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1002xxx/GSD-2022-1002116.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
