Memory Leak Vulnerability in iommu/vt-d Package
Summary
GSD-2022-1000173: iommu/vt-d: Fix potential memory leak in intel_setup_irq_remapping(). Affects Kernel versions >= 36f7355545725c5e9400520ae33e6ee16cf78c0e, < 5c43d46daa0d2928234dd2792ebebc35d29ee2d1. 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 enables secure and efficient device assignment in virtualized environments. The package is responsible for managing the remapping of interrupts to devices. This vulnerability affects versions of the Linux Kernel from v5.4.54 to v5.4.177.
Vulnerability Detail
The vulnerability identified in the iommu/vt-d package is a potential memory leak in the intel_setup_irq_remapping() function. This function is responsible for setting up interrupt remapping for Intel VT-d. 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 to the patched version.
Conclusion
The memory leak vulnerability in the iommu/vt-d package of the Linux Kernel can potentially lead to system instability and denial-of-service conditions. It is crucial to update the Linux Kernel to version v5.4.178 or later to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This 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 analyze and alert you if the vulnerability is present.
At the time of this report, there are no known exploits for this vulnerability. However, it is important to promptly apply the recommended fix to mitigate any potential risks.
No, this vulnerability requires local access to the system in order to exploit it.
For more details about this vulnerability, you can refer to the source JSON file provided by the Cloud Security Alliance's GSD Database: https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1000xxx/GSD-2022-1000173.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
