Uninitialized Use Vulnerability in bonding Package
Summary
GSD-2021-1000852: bonding: init notify_work earlier to avoid uninitialized use. Affects Kernel versions < 1fb72dd4bcbce6eca085f7c1403e5b03d4e70f83. 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 bonding package is a component of the Linux Kernel that provides network bonding functionality. It allows multiple network interfaces to be combined into a single logical interface, providing fault tolerance and load balancing. The vulnerability in the bonding package arises from a failure to initialize the notify_work structure, leading to potential uninitialized use.
Vulnerability Detail
The vulnerability in the bonding package occurs due to the delayed initialization of the notify_work structure. This can result in uninitialized use of the structure, potentially leading to undefined behavior and security issues. Attackers may be able to exploit this vulnerability to execute arbitrary code, escalate privileges, or cause a denial-of-service condition. The vulnerability has been fixed in Linux Kernel version v4.14.237 by commit 1fb72dd4bcbce6eca085f7c1403e5b03d4e70f83.
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 uninitialized use vulnerability in the bonding package of the Linux Kernel can have serious security implications. It is crucial to update to the fixed version or apply the specific commit to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially allow attackers to execute arbitrary code, escalate privileges, or cause a denial-of-service condition.
At the time of this report, there is no known exploit for this vulnerability.
The vulnerability affects versions of the Linux Kernel prior to v4.14.237.
Yes, the vulnerability has been fixed in Linux Kernel version v4.14.237 by commit 1fb72dd4bcbce6eca085f7c1403e5b03d4e70f83.
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 the Vulert Playground will analyze it for open-source vulnerabilities.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
