Use-after-free vulnerability in net: bonding package

Kernel Updated 02 Oct 2025

Summary

31/07/2022
N/A
No i
Unrated
Not published

GSD-2022-1004724: net: bonding: fix use-after-free after 802.3ad slave unbind. Affects Kernel versions >= 0622cab0341cac6b30da177b0faa39fae0680e71, < 893825289ba840afd86bfffcb6f7f363c73efff8. 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 net: bonding package is a component of the Linux Kernel that provides support for network bonding, allowing multiple network interfaces to function as a single bonded interface. This package is responsible for managing the bonding of network interfaces and ensuring fault tolerance and load balancing. The vulnerability identified in this package can lead to a use-after-free condition, which occurs when a program continues to use a memory address after it has been freed. This can result in various security issues, including potential remote code execution or denial of service attacks.

Vulnerability Detail

The use-after-free vulnerability in the net: bonding package occurs after an 802.3ad slave is unbound. This vulnerability was introduced in version v4.7 of the Linux Kernel and was fixed in version v5.4.204. When an 802.3ad slave is unbound, a use-after-free condition can be triggered, potentially allowing an attacker to exploit the freed memory. The impact and attack plausibility of this vulnerability have not been proven, but it is essential to address it to ensure the security and stability of the system.

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, users can consider implementing general security best practices such as restricting network access and applying other relevant security measures to reduce the risk of exploitation.

Conclusion

The use-after-free vulnerability in the net: bonding package can pose a significant security risk if left unaddressed. It is crucial to update the Linux Kernel to version v5.4.204 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

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

A use-after-free vulnerability occurs when a program continues to use a memory address after it has been freed. This can lead to various security issues, including potential remote code execution or denial of service attacks.

The use-after-free vulnerability in the net: bonding package can potentially be exploited by an attacker to execute arbitrary code or launch denial of service attacks. However, the impact and attack plausibility have not been proven.

This vulnerability was introduced in version v4.7 of the Linux Kernel and was fixed in version v5.4.204. Users running versions between these two should consider updating to a fixed version.

There is no specific workaround mentioned for this vulnerability. However, users can implement general security best practices to reduce the risk of exploitation.

Related vulnerabilities

Recent vulnerabilities recorded for Kernel.

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 →

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