net: tipc: fix possible refcount leak in tipc_sk_create()
Summary
GSD-2022-1004383: net: tipc: fix possible refcount leak in tipc_sk_create(). Affects Kernel versions < 833ecd0eae76eadf81d6d747bb5bc992d1151867. 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 'net' package in the Linux Kernel is responsible for handling network-related functionalities. It includes various protocols and drivers for communication between network devices. One of these protocols is TIPC (Transparent Inter-Process Communication), which provides reliable and ordered message delivery between processes. The 'tipc_sk_create()' function is used to create a new TIPC socket. However, a vulnerability has been discovered in this function that could lead to a reference count leak.
Vulnerability Detail
The vulnerability in the 'tipc_sk_create()' function could result in a refcount leak. This means that the reference count of a TIPC socket may not be properly decremented, leading to a resource leak. An attacker could potentially exploit this vulnerability to exhaust system resources, causing a denial-of-service condition. 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
No workaround has been mentioned for this vulnerability.
Conclusion
The 'net: tipc: fix possible refcount leak in tipc_sk_create()' vulnerability in the Linux Kernel has the potential to cause a denial-of-service condition. It is recommended to update the Linux Kernel to version v5.15.56 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is a potential denial-of-service condition due to resource exhaustion.
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 and the playground will provide real-time alerts for open-source vulnerabilities.
No known exploit has been reported for this vulnerability at the moment.
The specific conditions required for exploiting this vulnerability have not been disclosed yet.
For more details about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
