net: tun: avoid disabling NAPI twice in Kernel
Summary
GSD-2022-1004221: net: tun: avoid disabling NAPI twice. Affects Kernel versions >= 872c6c9eee952a0fdb33de440c358155ef87b854, < b74a3789768c039182a45903b9f584b090d25117. 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 Kernel is a critical component of the Linux operating system that provides core functionality and interfaces with hardware devices. It handles tasks such as process management, memory management, and device drivers. The 'net' subsystem in the Kernel is responsible for networking functionality, including the implementation of network protocols and device drivers. The 'tun' driver is a virtual network device driver that allows user-space programs to interact with the Kernel's networking stack. It provides a way to create virtual network interfaces and handle network traffic. However, a vulnerability has been discovered in the 'tun' driver that can lead to the disabling of NAPI (New API) twice, potentially causing performance issues and instability in the networking subsystem.
Vulnerability Detail
The vulnerability in the 'tun' driver occurs when NAPI is disabled twice. NAPI is a feature in the Kernel that improves network performance by reducing CPU usage during high network traffic. When NAPI is disabled twice, it can result in unnecessary overhead and decreased network performance. This vulnerability can be exploited by an attacker to degrade the performance of a system's networking subsystem, potentially leading to denial-of-service (DoS) attacks or other network-related issues. The vulnerability was introduced in Linux Kernel version v5.18.10 by commit 872c6c9eee952a0fdb33de440c358155ef87b854 and has been fixed in version v5.18.10 by commit b74a3789768c039182a45903b9f584b090d25117.
How To Fix
No fixed version is published for this vulnerability.
To fix this vulnerability, it is recommended to update the Linux Kernel to version v5.18.10 or later. This can be done by downloading the latest Kernel source code from the official repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compiling it according to the system's specifications. Alternatively, users can wait for their Linux distribution to provide an updated Kernel package and install it through the package manager. It is important to regularly update the Kernel to ensure the latest security patches and bug fixes are applied.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary workaround, users can manually disable NAPI only once in the 'tun' driver configuration. This can be done by modifying the driver's source code or configuration files. However, it is recommended to apply the official fix by updating the Kernel to avoid any potential issues or regressions.
Conclusion
The 'net: tun: avoid disabling NAPI twice' vulnerability in the Kernel's 'tun' driver can lead to decreased network performance and potential instability in the networking subsystem. It is recommended to update the Linux Kernel to version v5.18.10 or later to fix this vulnerability. Users can also apply a temporary workaround by manually disabling NAPI only once in the 'tun' driver configuration. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to decreased network performance and potential instability in the networking subsystem. It can be exploited by attackers to degrade the performance of a system's networking capabilities, potentially leading to denial-of-service (DoS) attacks or other network-related issues.
You can use tools like Vulert (https://vulert.com) 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 in the software. You can also visit the Vulert Playground (https://vulert.com/scanner) to check if your application is affected without any signup.
Yes, a temporary workaround is to manually disable NAPI only once in the 'tun' driver configuration. This can be done by modifying the driver's source code or configuration files. However, it is recommended to apply the official fix by updating the Kernel to avoid any potential issues or regressions.
To update the Linux Kernel, you can download the latest source code from the official repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and compile it according to your system's specifications. Alternatively, you can wait for your Linux distribution to provide an updated Kernel package and install it through the package manager.
At the time of this report, there are no known exploits for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.