Memory Leak Vulnerability in crypto: sa2ul
Summary
GSD-2021-1000381: crypto: sa2ul - Fix memory leak of rxd. Affects Kernel versions >= 00c9211f60db2dead16856f81a3e6ab86b31f275, < 0e596b3734649041ed77edc86a23c0442bbe062b. 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: sa2ul package is a component of the Linux Kernel, which is responsible for providing cryptographic functionality. It is used to perform various cryptographic operations such as encryption, decryption, and hashing. The sa2ul module specifically handles the processing of received data (rxd).
Vulnerability Detail
The vulnerability in the crypto: sa2ul package is related to a memory leak issue in the handling of received data (rxd). When processing incoming data, the module fails to release allocated memory, leading to a memory leak. This can result in the exhaustion of available memory resources, potentially causing system instability or denial of service conditions. The vulnerability was introduced in version v5.10 of the Linux Kernel and has been fixed in version v5.10.37.
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
No workaround has been provided for this vulnerability.
Conclusion
The memory leak vulnerability in the crypto: sa2ul package can be fixed by updating the Linux Kernel to version v5.10.37 or later. It is recommended to apply the necessary updates to ensure the security and stability of the system. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The memory leak vulnerability in the crypto: sa2ul package can lead to the exhaustion of available memory resources, potentially causing system instability or denial of service conditions.
You can use the Vulert playground (https://vulert.com/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 vulnerability.
No known exploit has been reported for this vulnerability at the moment.
The recommended mitigation is to update the Linux Kernel to version v5.10.37 or later, which includes the fix for this memory leak vulnerability.
You can find more information about this vulnerability in the GSD-2021-1000381.json file available in the GSD database repository (https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/GSD-2021-1000381.json).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
