Memory Leak in net: bridge: vlan

Kernel Updated 02 Oct 2025

Summary

27/02/2022
N/A
No i
Unrated
Not published

GSD-2022-1000634: net: bridge: vlan: fix memory leak in __allowed_ingress. Affects Kernel versions >= a580c76d534c7360ba68042b19cb255e8420e987, < 14be8d448fca6fe7b2a413831eedd55aef6c6511. 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: bridge: vlan package is a component of the Linux Kernel that handles VLAN functionality within network bridges. It allows for the creation and management of virtual LANs (VLANs) on a bridge device. VLANs are used to segment network traffic and improve network performance and security. However, a vulnerability has been discovered in this package that can lead to a memory leak.

Vulnerability Detail

The vulnerability in net: bridge: vlan is caused by a memory leak in the __allowed_ingress function. This function is responsible for handling ingress filtering for VLAN packets. Due to a coding error, memory allocated during the ingress filtering process is not properly freed, leading to a memory leak. An attacker could potentially exploit this vulnerability to exhaust system memory resources, resulting in a denial-of-service condition. The vulnerability was introduced in version v5.6 of the Linux Kernel and has been fixed in version v5.16.5.

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 known workaround for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel.

Conclusion

The memory leak vulnerability in net: bridge: vlan can be mitigated by updating the Linux Kernel to version v5.16.5 or later. This will ensure that the __allowed_ingress function properly frees allocated memory, preventing potential memory exhaustion and denial-of-service attacks. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

Net: bridge: vlan is a component of the Linux Kernel that handles VLAN functionality within network bridges. It allows for the creation and management of virtual LANs (VLANs) on a bridge device.

A memory leak is a type of software bug where allocated memory is not properly freed, leading to a gradual loss of available memory resources. In this case, the memory leak occurs in the __allowed_ingress function of net: bridge: vlan.

The vulnerability can be exploited by an attacker to exhaust system memory resources, potentially leading to a denial-of-service condition.

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 the Vulert Playground will analyze it for any open-source vulnerabilities, including this one.

Yes, the vulnerability has been fixed in version v5.16.5 of the Linux Kernel. It is recommended to update your system's Linux Kernel to this version or later.

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