Vulnerability in sch_cake Package: Calling cake_destroy() from cake_init()
Summary
GSD-2021-1002739: sch_cake: do not call cake_destroy() from cake_init(). Affects Kernel versions >= 046f6fd5daefac7f5abdafb436b30f63bc7c602b, < f6deae2e2d83bd267e1986f5d71d8c458e18fd99. 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 sch_cake package is a component of the Linux Kernel, which is responsible for managing network traffic shaping. It utilizes the Cake queuing discipline algorithm to prioritize and control the flow of packets. The vulnerability in question arises from an incorrect implementation within the package's initialization function, cake_init(). Specifically, the function erroneously calls cake_destroy(), leading to potential issues during the initialization process.
Vulnerability Detail
The vulnerability occurs due to the improper invocation of cake_destroy() within cake_init(). This can result in various consequences, such as memory corruption, system instability, or even potential privilege escalation attacks. The vulnerability was introduced in version v4.19 of the Linux Kernel and has been fixed in version v5.15.11.
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 this vulnerability has been fixed in the latest version of the Linux Kernel, there is no specific workaround available. It is advisable to update to the patched version to ensure the mitigation of this vulnerability.
Conclusion
In conclusion, the sch_cake package in the Linux Kernel is vulnerable to an issue where cake_destroy() is mistakenly called from cake_init(). This vulnerability can lead to memory corruption, system instability, or privilege escalation attacks. It is crucial to update to the fixed version of the Linux Kernel (v5.15.11 or later) to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to memory corruption, system instability, or privilege escalation attacks.
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 alerts for any open-source vulnerabilities, including this one.
No, as the vulnerability has been fixed in the latest version of the Linux Kernel, it is recommended to update to the patched version.
The vulnerability was introduced in version v4.19 of the Linux Kernel and has been fixed in version v5.15.11.
You can find more details about this vulnerability in the Open Source Vulnerability Database at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1002xxx/GSD-2021-1002739.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
