Memory Leak in net: bridge: vlan
Summary
GSD-2022-1000267: net: bridge: vlan: fix memory leak in __allowed_ingress. Affects Kernel versions >= a580c76d534c7360ba68042b19cb255e8420e987, < c5e216e880fa6f2cd9d4a6541269377657163098. 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 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 segregate network traffic and improve network efficiency. 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. When processing VLAN ingress traffic, memory is allocated but not properly freed, resulting in a continuous accumulation of memory over time. This can lead to resource exhaustion and potential denial of service (DoS) attacks. The vulnerability was introduced in version v5.6 of the Linux Kernel and has been fixed in version v5.15.19.
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 necessary to apply the fix by updating the Linux Kernel.
Conclusion
The memory leak vulnerability in net: bridge: vlan can have serious consequences, including resource exhaustion and potential denial of service attacks. It is crucial to update the Linux Kernel to version v5.15.19 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
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 occurs when memory is allocated but not properly freed, leading to a continuous accumulation of memory over time. This can result in resource exhaustion and potential performance issues or crashes.
The vulnerability in net: bridge: vlan can lead to a memory leak, which can cause resource exhaustion and potential denial of service (DoS) attacks. It may result in degraded system performance or even system crashes.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file, and Vulert will analyze it for any open-source vulnerabilities, including this one.
To update the Linux Kernel, you can fetch the latest kernel source code from the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compile it according to the provided instructions. Alternatively, you can wait for your Linux distribution to release an updated kernel package that includes the fix.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
