net:sfc: Fix Non-Freed IRQ in Legacy IRQ Mode in Kernel

Kernel Updated 02 Oct 2025

Summary

30/06/2021
N/A
No i
Unrated
Not published

GSD-2021-1000942: net:sfc: fix non-freed irq in legacy irq mode. Affects Kernel versions < 8d717c9135a3340ae62d1699484850bfb4112b0c. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It manages system resources, including memory, processes, and input/output operations. The vulnerability affects the net:sfc module, which is responsible for handling network traffic on Solarflare network adapters. In legacy IRQ mode, there is a flaw that prevents the proper release of IRQ resources, leading to potential resource exhaustion and system instability.

Vulnerability Detail

The vulnerability arises due to a failure to free IRQ resources in legacy IRQ mode. When network traffic is processed by the net:sfc module, IRQs are allocated to handle interrupts. However, in legacy IRQ mode, these IRQs are not properly released after processing, resulting in a gradual depletion of available IRQ resources. This can lead to resource exhaustion, causing system instability and potential denial-of-service conditions. An attacker may be able to exploit this vulnerability to disrupt network communication or crash the system.

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 using legacy IRQ mode in the net:sfc module. Instead, they can switch to a different IRQ mode supported by the module, such as MSI-X or MSI. This can be achieved by modifying the configuration of the network adapter or the Kernel module parameters. However, it is recommended to apply the official fix by updating the Kernel to ensure comprehensive vulnerability mitigation.

Conclusion

The net:sfc module in the Kernel is susceptible to a vulnerability that can result in resource exhaustion and system instability. By not properly freeing IRQ resources in legacy IRQ mode, the module can experience a gradual depletion of available resources, potentially leading to denial-of-service conditions. It is crucial to update the Kernel to version v5.10.44 or later, which includes the fix for this vulnerability. Alternatively, users can switch to a different IRQ mode supported by the module as a temporary workaround. For further assistance or information, please contact DevNack.com.

See every vulnerability recorded for Kernel →

Share this vulnerability

FAQ

The vulnerability can lead to resource exhaustion and system instability. It may allow an attacker to disrupt network communication or crash the 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 Vulert will analyze it for any open-source vulnerabilities, including this one.

At the time of this report, no known exploits for this vulnerability have been disclosed. However, it is crucial to apply the recommended fix or workaround to prevent potential exploitation.

Yes, this vulnerability can be exploited remotely. An attacker with network access to the affected system could potentially exploit the vulnerability to disrupt network communication or crash the system.

For further support on vulnerability remediation or any other security concerns, you can reach out to info@devnack.com. Our team of experts will be happy to assist you.

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