net/smc: Incorrect list_del in smc_lgr_cleanup_early
Summary
GSD-2021-1002568: net/smc: fix wrong list_del in smc_lgr_cleanup_early. Affects Kernel versions >= a0a62ee15a829ebf8aeec55a4f1688230439b3e0, < 95518fe354d712dca6f431cf2a11b8f63bc9a66c. 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 allows for efficient communication between systems. The smc_lgr_cleanup_early function in this package is responsible for cleaning up resources during early termination of an SMC connection. However, there is a vulnerability in the implementation of this function that can lead to incorrect removal of an entry from a linked list.
Vulnerability Detail
The vulnerability arises from a wrong list_del operation in the smc_lgr_cleanup_early function. This can result in the removal of an incorrect entry from the linked list, leading to potential memory corruption or other unexpected behavior. An attacker may be able to exploit this vulnerability to manipulate the linked list and potentially execute arbitrary code or cause a denial-of-service condition.
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.
Conclusion
The net/smc package in the Linux Kernel is vulnerable to an incorrect list_del operation in the smc_lgr_cleanup_early function. This can lead to memory corruption or other unexpected behavior, potentially allowing an attacker to execute arbitrary code or cause a denial-of-service condition. It is recommended to update the Linux Kernel to version v5.15.7 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to memory corruption or other unexpected behavior. An attacker may be able to exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition.
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 Vulert will analyze it for any open-source vulnerabilities, including this one.
No, there is no known workaround for this vulnerability. It is recommended to update the Linux Kernel to the latest version to apply the fix.
Yes, this vulnerability can potentially be exploited remotely if an attacker is able to send malicious network traffic to the affected system.
There are no known instances of this vulnerability being exploited in the wild at this time.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
