net/smc: Remove Device from smcd_dev_list after Failed device_add()
Summary
UVI-2021-1000580: net/smc: remove device from smcd_dev_list after failed device_add(). Affects Kernel versions >= c6ba7c9ba43de1b57e9a53946e7ff988554c84ed, < 8b2cdc004d21a7255f219706dca64411108f7897. 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/smc package is a part of the Linux Kernel ecosystem. It provides support for the SMC (System Management Controller) protocol, which is used for communication between systems. The smcd_dev_list is a list of SMC devices maintained by the package. This vulnerability arises when a device fails to be added to the smcd_dev_list, but is not removed from the list. This can lead to inconsistencies and potential security issues within the system.
Vulnerability Detail
The vulnerability occurs due to a failure to remove a device from the smcd_dev_list after a failed device_add() operation. This can result in the device remaining in the list, even though it is not functional or properly configured. An attacker could potentially exploit this vulnerability to manipulate the device list and cause system instability or gain unauthorized access. The vulnerability was introduced in version v4.19 of the Linux Kernel and has been fixed in version v5.10.42.
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 net/smc vulnerability allows a device to remain in the smcd_dev_list after a failed device_add() operation, potentially leading to system instability and unauthorized access. It is crucial to update the Linux Kernel to version v5.10.42 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to system instability and unauthorized access.
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 it will provide real-time alerts for open-source vulnerabilities.
There is no known exploit for this vulnerability at the moment.
The recommended mitigation is to update the Linux Kernel to the fixed version.
The vulnerability was discovered by an automated security analysis tool.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
