Use-after-free vulnerability in i40e_client_subtask() in Kernel
Summary
GSD-2021-1000410: i40e: Fix use-after-free in i40e_client_subtask(). Affects Kernel versions >= 7b0b1a6d0ac983ce1928432285d0222d4fb7c38b, < d718c15a2bf9ae082d5ae4d177fb19ef23cb4132. 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 fundamental component of the Linux operating system that provides core services and functions. It acts as an interface between the hardware and software layers, managing resources and facilitating communication between different components. The i40e_client_subtask() function is a part of the i40e driver, which is responsible for managing Intel Ethernet Connection X710/XL710 devices. This vulnerability affects the Kernel and specifically the i40e_client_subtask() function.
Vulnerability Detail
The use-after-free vulnerability in i40e_client_subtask() allows an attacker to exploit a freed memory region, leading to potential code execution or a system crash. This vulnerability was introduced in version v4.16 of the Linux Kernel and was fixed in version v5.4.120. 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 →
Conclusion
The use-after-free vulnerability in i40e_client_subtask() in the Kernel can potentially lead to code execution or system crashes. It is crucial to update to the fixed version of the Linux Kernel (v5.4.120 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 could potentially allow an attacker to execute arbitrary code or crash the system.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground and it will alert you in real-time if any open-source vulnerabilities, including this one, are detected.
At the moment, there are no known workarounds for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.
Yes, this vulnerability was introduced in version v4.16 of the Linux Kernel and was fixed in version v5.4.120.
There is currently no evidence of this vulnerability being actively exploited.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
