Vulnerability in Kernel package: tipc: move bc link creation back to tipc_node_create
Summary
GSD-2022-1004438: tipc: move bc link creation back to tipc_node_create. Affects Kernel versions >= 4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4, < 35fcb2ba35b4d9b592b558c3bcc6e0d90e213588. 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 package is a critical component of the Linux operating system, responsible for managing the core functionalities and communication between hardware and software. It provides essential services and functions for the proper functioning of the system. The vulnerability in focus affects the tipc module within the Kernel package.
Vulnerability Detail
The vulnerability arises from an incorrect placement of bc (broadcast) link creation in the tipc_node_create function. This misplacement can potentially lead to security vulnerabilities, although the exact impact and attack vectors have not been proven yet. The vulnerability was introduced in version v5.5 of the Linux Kernel by commit 4cbf8ac2fe5a0846508fe02b95a5de1a90fa73f4 and has been fixed in version v5.15.53 by commit 35fcb2ba35b4d9b592b558c3bcc6e0d90e213588.
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 specific workaround has been mentioned for this vulnerability.
Conclusion
The vulnerability in the Kernel package, specifically in the tipc module, has been identified and fixed in version v5.15.53. It is crucial to update the Linux Kernel package to the recommended version to mitigate potential security risks. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The exact impact of this vulnerability is yet to be determined. However, it has the potential to introduce security vulnerabilities in the affected 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 and the Vulert Playground will analyze it for potential vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is always recommended to apply security updates promptly to mitigate potential risks.
The primary solution to fix this vulnerability is to update the Linux Kernel package to the recommended version. There are no known alternative solutions mentioned.
You can find more information about this vulnerability in the official Linux Kernel security advisories or by referring to the provided references in the vulnerability details section.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
