net: tipc: Fix Possible Refcount Leak in tipc_sk_create()
Summary
GSD-2022-1004692: net: tipc: fix possible refcount leak in tipc_sk_create(). Affects Kernel versions < 4919d82f7041157a421ca9bf39a78551d5ad8a1b. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Linux Kernel is an open-source monolithic Unix-like computer operating system kernel. It provides the core functionality for the Linux operating system. The tipc (Transparent Inter-Process Communication) protocol is a socket-based communication protocol used for communication between processes on different nodes in a cluster. The tipc_sk_create() function is responsible for creating a new tipc socket. However, there is a potential refcount leak in this function, which can lead to resource exhaustion and other security issues.
Vulnerability Detail
The vulnerability in the tipc_sk_create() function can result in a refcount leak. This means that the reference count of a socket is not properly managed, leading to a potential resource leak. An attacker could exploit this vulnerability to exhaust system resources, causing denial of service conditions or other security issues. 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 tipc_sk_create() function in the Linux Kernel is vulnerable to a potential refcount leak. This vulnerability has been fixed in Linux Kernel version v5.4.207. Users are advised to update their Linux Kernel to the latest version to ensure the security of their systems. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability can include resource exhaustion, denial of service conditions, and other security issues.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities in the software.
No, the impact and attack plausibility of this vulnerability have not been proven yet, and there is no known exploit at the moment.
The recommended mitigation is to update the Linux Kernel to version v5.4.207 or later, which includes the fix for this vulnerability.
You can find more information about this vulnerability in the GSD-2022-1004692 JSON file available at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1004xxx/GSD-2022-1004692.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
