Vulnerability in ixgbe package: Panic when setting sriov_numvfs to zero

Kernel Updated 02 Oct 2025

Summary

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

GSD-2022-1004340: ixgbe: Add locking to prevent panic when setting sriov_numvfs to zero. Affects Kernel versions >= d773d1310625be3b040b436178ad59a0af8888f1, < 16f929a5e76fd047fd8697e1e568bdd7d771955c. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The ixgbe package is a driver for Intel 10 Gigabit Ethernet (10GbE) network adapters. It provides support for various features and configurations of these network adapters. One of the functionalities it offers is the ability to set the number of virtual functions (VFs) using the sriov_numvfs parameter. VFs allow for the partitioning of a physical network adapter into multiple virtual instances, each with its own MAC address and network resources. However, a vulnerability has been discovered in the ixgbe package that can lead to a panic when setting sriov_numvfs to zero.

Vulnerability Detail

The vulnerability in the ixgbe package arises from a lack of locking when setting the sriov_numvfs parameter to zero. 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 operation of the affected system. The vulnerability was introduced in version v3.6 of the Linux Kernel and has been fixed in version v5.15.58 by commit 16f929a5e76fd047fd8697e1e568bdd7d771955c.

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

If updating the Kernel is not immediately feasible, a temporary workaround can be implemented by avoiding the setting of sriov_numvfs to zero. Instead, set it to a non-zero value to prevent triggering the vulnerability. For example, if the desired number of VFs is zero, set sriov_numvfs to one or any other non-zero value.

Conclusion

The vulnerability in the ixgbe package that can cause a panic when setting sriov_numvfs to zero has been identified and fixed in version v5.15.58 of the Linux Kernel. It is recommended to update the Kernel to this version or a later one to mitigate the vulnerability. If immediate updating is not possible, a temporary workaround can be implemented by setting sriov_numvfs to a non-zero value. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to a system panic, causing the affected system to crash and potentially disrupt its operation.

No, this vulnerability requires the ability to modify the sriov_numvfs parameter, which typically requires local or privileged access to the system.

There are no known instances of this vulnerability being exploited in the wild at this time.

Yes, the vulnerability has been fixed in version v5.15.58 of the Linux Kernel. Updating to this version or a later one will address the issue.

For more details about this vulnerability, including its technical aspects and the specific commits that fixed it, refer to the provided references link.

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