net: tun: stop NAPI when detaching queues
Summary
GSD-2022-1004236: net: tun: stop NAPI when detaching queues. Affects Kernel versions >= 943170998b200190f99d3fe7e771437e2c51f319, < 872c6c9eee952a0fdb33de440c358155ef87b854. 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 package in the Linux ecosystem is responsible for managing the core functionality of the operating system. It provides essential services and functions to enable the proper functioning of the system. One of the components within the Kernel package is the 'net' module, which handles network-related operations. The 'tun' driver is a part of the 'net' module and is responsible for creating virtual network interfaces. These interfaces are used for various purposes, such as VPN connections and virtualization. However, a vulnerability has been discovered in the 'tun' driver that can lead to potential security risks.
Vulnerability Detail
The vulnerability in the 'tun' driver occurs when detaching queues. The driver fails to stop NAPI (New API) when detaching queues, which can result in a security vulnerability. NAPI is a mechanism used in network drivers to improve performance by reducing CPU usage. By not stopping NAPI when detaching queues, an attacker may be able to exploit this vulnerability to gain unauthorized access, execute arbitrary code, or cause a denial-of-service (DoS) attack. 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
There is no specific workaround mentioned for this vulnerability.
Conclusion
The 'net: tun: stop NAPI when detaching queues' vulnerability in the Kernel package's 'tun' driver poses a potential security risk. It is recommended to update the Linux Kernel package to version v5.18.10 or later to mitigate 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, an attacker may gain unauthorized access, execute arbitrary code, or cause a denial-of-service (DoS) attack.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just a manifest file like package-lock.json.
Yes, the vulnerability has been fixed in Linux Kernel version v5.18.10. It is recommended to update the Kernel package to this version or later to mitigate the security risk.
The remote exploitability of this vulnerability is not yet proven. Further analysis is required to determine if remote exploitation is possible.
There are no known instances of this vulnerability being exploited at the moment. However, it is important to apply the recommended fix to ensure the system is protected.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.