Memory Leak in iommu/amd Package
Summary
GSD-2022-1000763: iommu/amd: Fix I/O page table memory leak. Affects Kernel versions >= e42ba0633064ef23eb1c8c21edf96bac1541bd4b, < 378e2fe1eb58d5c2ed55c8fe5e11f9db5033cdd6. 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/amd package is a component of the Linux Kernel that provides support for Input/Output Memory Management Units (IOMMUs) on AMD processors. IOMMUs are responsible for mapping and translating memory addresses between devices and the CPU. The iommu/amd package is crucial for ensuring secure and efficient data transfers between devices and the CPU. However, a vulnerability has been discovered in this package that can lead to a memory leak.
Vulnerability Detail
The vulnerability in the iommu/amd package results in a memory leak in the I/O page table. When this vulnerability is exploited, memory resources are not properly released, leading to a gradual depletion of available memory. This can eventually cause system instability, performance degradation, and even denial-of-service conditions. The vulnerability was introduced in version v5.12 of the Linux Kernel and has been fixed in version v5.15.27.
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 essential to apply the recommended fix by updating the Linux Kernel to the patched version.
Conclusion
The memory leak vulnerability in the iommu/amd package can have severe consequences on system stability and performance. It is crucial to update the Linux Kernel to version v5.15.27 or later to address this issue. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a memory leak, causing system instability, performance degradation, and potential 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 provide real-time alerts for open-source vulnerabilities.
At the time of this report, there is no known exploit for this vulnerability. However, it is crucial to apply the recommended fix to mitigate any potential risks.
This vulnerability requires local access to the affected system. It cannot be exploited remotely over a network.
The recommended solution is to update the Linux Kernel to the patched version. There are no known alternative solutions or workarounds.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
