Memory Leak Vulnerability in crypto: sun8i-ss
Summary
GSD-2021-1000293: crypto: sun8i-ss - Fix memory leak of object d when dma_iv fails to map. Affects Kernel versions >= ac2614d721dea2ff273af19c6c5d508d58a2bb3e, < 6516cb852d704ff8d615de1f93cd443a99736c3d. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The crypto: sun8i-ss package is a component of the Linux Kernel that provides cryptographic operations for the Allwinner sun8i SoC family. It includes hardware acceleration for encryption and decryption algorithms. The vulnerability in this package relates to a memory leak issue that occurs when the dma_iv fails to map.
Vulnerability Detail
The memory leak vulnerability in crypto: sun8i-ss arises when the dma_iv fails to map. This can lead to a continuous allocation of memory objects without proper deallocation, resulting in memory exhaustion. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) condition by consuming excessive memory resources. The vulnerability was introduced in version v5.10 of the Linux Kernel and has been fixed in version v5.12.4.
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. However, applying the recommended fix by updating the Linux Kernel to the latest version will mitigate the issue.
Conclusion
The memory leak vulnerability in crypto: sun8i-ss can lead to a denial-of-service condition by causing memory exhaustion. It is crucial to update the Linux Kernel to version v5.12.4 or later to fix this issue. By applying the recommended fix, the dma_iv mapping failure will be handled correctly, preventing memory leaks and ensuring proper deallocation of memory objects. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a denial-of-service (DoS) condition by causing memory exhaustion. This can potentially disrupt the normal functioning of the affected system.
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 memory leak issue.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the recommended fix to prevent any potential exploitation.
No, this vulnerability does not have a remote exploit vector. An attacker would need local access to the affected system to exploit the memory leak issue.
The recommended solution is to update the Linux Kernel to the latest version. This ensures that the memory leak issue is fixed. There are no alternative solutions mentioned for this specific vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
