Memory Leak of Pad in crypto: sun8i-ss
Summary
GSD-2021-1000286: crypto: sun8i-ss - Fix memory leak of pad. Affects Kernel versions >= d9b45418a91773b7672e4c60037a28074b495c6d, < d3d702084d125689edb2b9395c707e09b471352e. 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: sun8i-ss package is a component of the Linux Kernel. It provides cryptographic operations for the sun8i-ss hardware. The sun8i-ss hardware is a cryptographic engine found in Allwinner SoCs. It is responsible for performing encryption and decryption operations. However, a memory leak vulnerability has been discovered in the pad functionality of the crypto: sun8i-ss package.
Vulnerability Detail
The memory leak vulnerability in the pad functionality of the crypto: sun8i-ss package can lead to a depletion of system memory resources. An attacker could potentially exploit this vulnerability to exhaust available memory, causing a denial of service (DoS) condition. The vulnerability was introduced in version v5.10 of the Linux Kernel and has been fixed in version v5.12.4. The fix involves the commit d3d702084d125689edb2b9395c707e09b471352e.
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 memory leak vulnerability in the pad functionality of the crypto: sun8i-ss package can be fixed by updating the Linux Kernel to version v5.12.4 or later. It is important to keep systems up to date with the latest security patches to mitigate potential risks. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a depletion of system memory resources, potentially causing a denial of service (DoS) condition.
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 analyze it for any open-source vulnerabilities, including this one.
Yes, a patch has been released in version v5.12.4 of the Linux Kernel. It is recommended to update to this version or later to fix the vulnerability.
The details of remote exploitation have not been provided. However, it is important to keep your system up to date with the latest security patches to mitigate potential risks.
There are no known instances of this vulnerability being exploited in the wild at the time of this report.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
