net/tls: Fix tls_sk_proto_close Executed Repeatedly in Linux Kernel
Summary
GSD-2022-1004629: net/tls: fix tls_sk_proto_close executed repeatedly. Affects Kernel versions >= 95fa145479fbc0a0c1fd3274ceb42ec03c042a4a, < e82376b632473790781a182b10823a4b5dbf6606. 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 Linux Kernel is the core component of the Linux operating system, responsible for managing system resources and providing essential services. The net/tls module in the Linux Kernel provides Transport Layer Security (TLS) support for network communication. TLS is a cryptographic protocol that ensures secure communication over a network. However, a vulnerability has been discovered in the net/tls module that allows the tls_sk_proto_close function to be executed repeatedly, leading to potential security issues.
Vulnerability Detail
The vulnerability in the net/tls module allows the tls_sk_proto_close function to be executed repeatedly. This can result in various security issues, such as resource exhaustion or memory corruption. An attacker could potentially exploit this vulnerability to cause a denial-of-service (DoS) attack or execute arbitrary code with kernel privileges. The vulnerability was introduced in Linux Kernel version 5.3 and has been fixed in version 5.10.127.
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 known workaround for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the latest version.
Conclusion
The net/tls module in the Linux Kernel is vulnerable to a security issue that allows the tls_sk_proto_close function to be executed repeatedly. This can lead to various security risks, including resource exhaustion and potential execution of arbitrary code with kernel privileges. To mitigate this vulnerability, it is crucial to update the Linux Kernel to version 5.10.127 or later. Regularly updating the Linux Kernel is essential to ensure the latest security patches are applied. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to various security issues, including resource exhaustion, memory corruption, and potential execution of arbitrary code with kernel privileges.
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.
There is no information available regarding exploitation of this vulnerability in the wild at the moment. However, it is always recommended to apply security patches and updates to mitigate any potential risks.
The only known mitigation for this vulnerability is to update the Linux Kernel to version 5.10.127 or later. It is important to regularly update the Linux Kernel to ensure the latest security patches are applied.
You can find more information about this vulnerability in the official Linux Kernel repository (https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/) and the vulnerability database maintained by the Cloud Security Alliance (https://github.com/cloudsecurityalliance/gsd-database).
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
