Vulnerability in Kernel - iommu/arm-smmu: Fix arm_smmu_device refcount leak in address translation
Summary
GSD-2021-1001196: iommu/arm-smmu: Fix arm_smmu_device refcount leak in address translation. Affects Kernel versions < 5f9741a9a91f25c89e04b408cd61e3ab050ce24b. 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 provides core functionalities and facilitates communication between hardware and software. It includes various subsystems, such as the iommu/arm-smmu, which handles address translation for input/output memory management units on ARM-based systems. The arm_smmu_device is a data structure that represents an instance of the ARM System MMU (SMMU) device. This vulnerability in the arm-smmu subsystem leads to a refcount leak in address translation, potentially impacting the stability and security of the system.
Vulnerability Detail
The vulnerability in the iommu/arm-smmu subsystem of the Kernel results in a refcount leak during address translation. This issue can be exploited by an attacker to cause memory leaks, leading to resource exhaustion and potential denial-of-service attacks. The refcount leak occurs when the arm_smmu_device is not properly released after address translation, causing a reference count imbalance. This vulnerability has been assigned the ID GSD-2021-1001196 and has been fixed in Linux Kernel version v5.13.4 by commit 5f9741a9a91f25c89e04b408cd61e3ab050ce24b.
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 →
Conclusion
The vulnerability in the iommu/arm-smmu subsystem of the Kernel can lead to memory leaks and resource exhaustion. It is crucial to update the Linux Kernel to version v5.13.4 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to memory leaks and resource exhaustion, potentially resulting in denial-of-service attacks and system instability.
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 and the Vulert service will analyze it for any open-source vulnerabilities, including this one.
No specific workaround has been provided for this vulnerability. It is recommended to update the Kernel to the fixed version.
At the time of this report, no known exploits have been disclosed for this vulnerability. However, it is crucial to apply the fix promptly to mitigate any potential risks.
You can find more information about the fix for this vulnerability in the Linux Kernel source code repository. The specific commit that addresses this issue is 5f9741a9a91f25c89e04b408cd61e3ab050ce24b.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
