Double Free Vulnerability in igbvf Package
Summary
GSD-2021-1002634: igbvf: fix double free in igbvf_probe. Affects Kernel versions >= d4e0fe01a38a073568aee541a0247fe734095979, < 8d0c927a9fb2b4065230936b77b54f857a3754fc. 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 igbvf package is a component of the Linux Kernel, which is responsible for providing support for Intel Gigabit Ethernet Virtual Function (VF) devices. It allows virtual machines to access the physical network interface through a virtual function. The igbvf package is widely used in virtualized environments to enable network connectivity for virtual machines.
Vulnerability Detail
The vulnerability identified in the igbvf package is a double free issue that occurs during the igbvf_probe function. This vulnerability was introduced in version v2.6.30 of the Linux Kernel and has been present until version v4.14.259. A double free vulnerability refers to a memory management flaw where a program attempts to free the same memory address twice, which can lead to memory corruption and potentially allow an attacker to execute arbitrary code or cause a denial-of-service (DoS) condition. The impact and attack plausibility of this vulnerability have not been proven yet.
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
As a workaround, users can avoid the vulnerability by not using the affected functionality or by disabling the igbvf driver if it is not required in their specific environment. However, it is strongly recommended to apply the official fix by updating the Linux Kernel to the latest version.
Conclusion
The double free vulnerability in the igbvf package of the Linux Kernel can potentially lead to memory corruption and other security issues. It is crucial to update the Linux Kernel to version v4.14.259 or later to mitigate this vulnerability. Users can also use Vulert's playground at https://vulert.com/scanner to check if their system is affected by this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven. However, if successfully exploited, it could lead to memory corruption, arbitrary code execution, or a denial-of-service (DoS) condition.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
The remote exploitability of this vulnerability has not been determined yet. Further analysis is required to assess the potential for remote exploitation.
The recommended mitigation is to update the Linux Kernel to version v4.14.259 or later, which includes the fix for this vulnerability. Additionally, users can disable the igbvf driver if it is not required in their environment.
At the moment, there is no publicly available proof-of-concept code for this vulnerability. However, it is important to apply the official fix by updating the Linux Kernel to the latest version.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.