Memory Leak Vulnerability in iommu/vt-d Package
Summary
GSD-2022-1000228: iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping(). Affects Kernel versions >= e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb, < 9d9995b0371e4e8c18d4f955479e5d47efe7b2d4. 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 iommu/vt-d package is a component of the Linux Kernel that provides support for Input-Output Memory Management Unit (IOMMU) and Virtualization Technology for Directed I/O (VT-d). It allows for efficient memory management and device isolation in virtualized environments. This package is widely used in Linux-based systems.
Vulnerability Detail
The vulnerability identified in the iommu/vt-d package is related to a potential memory leak in the intel_setup_irq_remapping() function. This function is responsible for setting up interrupt remapping for Intel IOMMU devices. The memory leak occurs when the function fails to properly release allocated memory in certain error scenarios. An attacker could potentially exploit this vulnerability to exhaust system memory resources, leading to a denial-of-service condition or other unpredictable behavior.
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 provided for this vulnerability. It is advised to apply the recommended fix by updating the Linux Kernel.
Conclusion
The memory leak vulnerability in the iommu/vt-d package can be mitigated by updating the Linux Kernel to version v5.10.99 or later. It is important to apply this fix to prevent potential memory exhaustion and system instability. For additional support and guidance, please reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability could potentially lead to a memory leak, causing system instability, resource exhaustion, or denial-of-service conditions.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.
At the time of this report, no known exploits have been reported for this vulnerability. However, it is still important to apply the recommended fix to mitigate any potential risks.
This vulnerability requires local access to the system to exploit. It cannot be exploited remotely over a network.
For further support on vulnerability remediation, you can contact info@devnack.com. They can provide assistance and guidance in addressing this vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
