Double list_add Vulnerability in Kernel
Summary
GSD-2022-1000711: iommu/vt-d: Fix double list_add when enabling VMD in scalable mode. Affects Kernel versions >= 474dd1c6506411752a9b2f2233eec11f1733a099, < d5ad4214d9c6c6e465c192789020a091282dfee7. 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 is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The vulnerability in question affects the Kernel's iommu/vt-d module when enabling VMD in scalable mode.
Vulnerability Detail
The vulnerability arises from a double list_add operation when enabling VMD in scalable mode within the iommu/vt-d module. This issue was introduced in version v5.14 of the Linux Kernel and fixed in version v5.16.13. The impact and attack plausibility of this vulnerability have not been proven yet. However, if exploited, it could potentially lead to security breaches, unauthorized access, or system instability. The specific technical details of the vulnerability can be found in the provided references.
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. It is advised to apply the fix by updating the Kernel to the recommended version.
Conclusion
The double list_add vulnerability in the Kernel's iommu/vt-d module when enabling VMD in scalable mode can potentially lead to security risks and system instability. It is crucial to update the Linux Kernel to version v5.16.13 or later to mitigate this vulnerability. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is currently unknown, as it has not been proven or exploited yet. However, if successfully exploited, it could lead to security breaches, unauthorized access, or system instability.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file, such as package-lock.json, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.
The recommended mitigation for this vulnerability is to update the Linux Kernel to version v5.16.13 or later, which includes the necessary fix. It is crucial to keep your system up to date with the latest security patches and updates.
The remote exploitability of this vulnerability is currently unknown. Further analysis and testing are required to determine if remote exploitation is possible.
You can find more information about this vulnerability, including technical details and the fix, in the provided references and the Vulert Database at https://vulert.com.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
