ixgbe: Locking Issue when Setting sriov_numvfs to Zero
Summary
GSD-2022-1004670: ixgbe: Add locking to prevent panic when setting sriov_numvfs to zero. Affects Kernel versions >= d773d1310625be3b040b436178ad59a0af8888f1, < 031af9e617a6f51075d97e56fc9e712c7dde2508. 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 ixgbe package is a network driver for Intel 10 Gigabit Ethernet (10GbE) Network Interface Cards (NICs). It provides support for various features, including Single Root I/O Virtualization (SR-IOV), which allows a single physical NIC to appear as multiple virtual NICs. The sriov_numvfs parameter is used to control the number of virtual functions (VFs) that can be created. However, a locking issue in the ixgbe driver can lead to a panic when setting sriov_numvfs to zero.
Vulnerability Detail
The vulnerability arises from a lack of proper locking when setting sriov_numvfs to zero in the ixgbe driver. This can result in a panic, causing the system to crash. An attacker with the ability to modify the sriov_numvfs parameter could exploit this vulnerability to disrupt the functioning of the affected system. The vulnerability was introduced in version v3.6 of the Linux Kernel and is fixed in version v5.4.208.
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.
Conclusion
The ixgbe driver in the Linux Kernel is vulnerable to a locking issue when setting sriov_numvfs to zero. This can result in a system crash. It is recommended to update the Linux Kernel to version v5.4.208 or later to fix this vulnerability. If you suspect your system may be affected, you can use the Vulert Playground to check for real-time alerts. For additional support, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a system crash (panic) when setting sriov_numvfs to zero, potentially causing disruption to the affected system.
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 it will provide real-time alerts for open-source vulnerabilities.
No, this vulnerability requires the ability to modify the sriov_numvfs parameter, which typically requires local access to the system.
There are no known instances of this vulnerability being exploited in the wild.
For further support on vulnerability remediation, you can contact info@devnack.com.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
