UAF in tlan_remove_one in Kernel
Summary
GSD-2021-1001408: net: ti: fix UAF in tlan_remove_one. Affects Kernel versions >= 1e0a8b13d35510e711fdf72e9a3e30bcb2bd49fa, < 0538b0ab7d2c396e385694228c7cdcd2d2c514e9. 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 crucial component of the Linux operating system that manages communication between hardware and software. It provides essential services and functions for the proper functioning of the system. The tlan_remove_one function in the Kernel is responsible for removing a network device from the system. However, a use-after-free (UAF) vulnerability has been discovered in this function.
Vulnerability Detail
The UAF vulnerability in tlan_remove_one arises from improper handling of network device removal. An attacker could exploit this vulnerability by manipulating the network device in a specific way, leading to a use-after-free condition. This could potentially result in a crash or allow the attacker to execute arbitrary code with kernel privileges. The vulnerability was introduced in version v3.10 of the Linux Kernel and was fixed in version v4.14.241.
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 v4.14.241 or later. This can be done by obtaining the latest version from the official Linux Kernel repository and following the installation instructions provided by the Kernel developers.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
No specific workaround has been mentioned for this vulnerability.
Conclusion
The UAF vulnerability in tlan_remove_one in the Kernel can lead to a use-after-free condition, potentially resulting in a system crash or arbitrary code execution with kernel privileges. It is crucial to update the Linux Kernel to version v4.14.241 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 can range from a system crash to potential execution of arbitrary code with kernel privileges.
You can use Vulert's playground at Vulert 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, there is no known public exploit for this vulnerability. However, it is important to apply the recommended fix to ensure the security of your system.
This vulnerability requires local access to the system in order to exploit it. Remote exploitation is not possible without prior access to the targeted system.
The recommended mitigation is to update the Linux Kernel to the fixed version. Additionally, it is always advisable to follow security best practices, such as restricting access to privileged accounts and implementing proper network security measures.
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.