Uninitialized Use Vulnerability in bonding Package

Kernel Updated 02 Oct 2025

Summary

29/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000828: bonding: init notify_work earlier to avoid uninitialized use. Affects Kernel versions < 818298d54aa0d7b3baf5635c94ff3b39b48d037f. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The bonding package is a part of the Linux Kernel ecosystem and is responsible for providing network bonding functionality. Network bonding allows multiple network interfaces to function as a single logical interface, providing fault tolerance and increased bandwidth. The bonding package is widely used in Linux-based systems to improve network reliability and performance.

Vulnerability Detail

The vulnerability in the bonding package involves uninitialized use of the notify_work structure. This issue occurs when the notify_work structure is not properly initialized before being used, leading to potential security vulnerabilities. An attacker could exploit this vulnerability to execute arbitrary code or cause a denial of service. The impact and attack plausibility of this vulnerability have not been proven yet.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.4.273 or later. This fix can be obtained by applying commit 818298d54aa0d7b3baf5635c94ff3b39b48d037f from the official Linux Kernel repository. Updating to the latest version will ensure that the notify_work structure is initialized correctly, mitigating the uninitialized use 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 can be fixed by updating the Linux Kernel to version v4.4.273 or later. It is recommended to apply commit 818298d54aa0d7b3baf5635c94ff3b39b48d037f from the official Linux Kernel repository. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The bonding package is a component of the Linux Kernel that enables network bonding, allowing multiple network interfaces to function as a single logical interface.

The impact of this vulnerability is not yet proven, but it could potentially allow an attacker to execute arbitrary code or cause a denial of service.

To fix this vulnerability, update the Linux Kernel to version v4.4.273 or later by applying commit 818298d54aa0d7b3baf5635c94ff3b39b48d037f from the official Linux Kernel repository.

No specific workaround has been mentioned for this vulnerability.

For more details about this vulnerability, you can refer to the source link provided in the Open Source Vulnerability database.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

How To Fix

No fixed version is published for this vulnerability.

To fix this vulnerability, it is recommended to update the Linux Kernel to version v4.4.273 or later. This fix can be obtained by applying commit 818298d54aa0d7b3baf5635c94ff3b39b48d037f from the official Linux Kernel repository. Updating to the latest version will ensure that the notify_work structure is initialized correctly, mitigating the uninitialized use vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback

Follow Vulert in Google

Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.