Memory Leak Vulnerability in iommu/vt-d Package
Summary
GSD-2022-1000669: iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping(). Affects Kernel versions >= e3beca48a45b5e0e6e6a4e0124276b8248dcc9bb, < b62eceb5f8f08815fe3f945fc55bbf997c344ecd. 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 Units (IOMMUs) and Virtualization Technology for Directed I/O (VT-d). IOMMUs are responsible for mapping device memory addresses to physical memory addresses, while VT-d allows for the isolation and protection of I/O devices in a virtualized environment. This vulnerability affects the package's intel_setup_irq_remapping() function.
Vulnerability Detail
The vulnerability in the intel_setup_irq_remapping() function of the iommu/vt-d package can lead to a potential memory leak. This function is responsible for setting up interrupt remapping for Intel VT-d 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. The vulnerability was introduced in version v5.8 of the Linux Kernel and has been fixed in version v5.16.8.
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 recommended to apply the fix by updating the Linux Kernel to the latest version.
Conclusion
The memory leak vulnerability in the iommu/vt-d package's intel_setup_irq_remapping() function can lead to system instability and resource exhaustion. It is crucial to update the Linux Kernel to version v5.16.8 or later to fix this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to a memory leak, which may result in system instability, resource exhaustion, or denial-of-service conditions.
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 to the playground and it will analyze and alert you if the vulnerability is present.
At the time of this report, there is no known exploit for this vulnerability. However, it is important to apply the fix as soon as possible to mitigate any potential risks.
This vulnerability does not have a direct remote exploit vector. However, an attacker with local access to the system may be able to exploit the vulnerability to cause system instability or resource exhaustion.
If you are unable to update the Kernel immediately, it is recommended to monitor system resources and ensure that memory usage does not reach critical levels. Implementing resource limits and monitoring tools can help detect and mitigate potential impacts of the vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
