Vulnerability in drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem
Summary
GSD-2022-1002585: drm/etnaviv: check for reaped mapping in etnaviv_iommu_unmap_gem. Affects Kernel versions < 64f4edec081cb7c97c5e928529d0e1b0dbbffb83. 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 drm/etnaviv package is a component of the Linux Kernel that provides support for the Etnaviv GPU found in certain embedded systems. It enables graphics rendering and acceleration capabilities on these devices. The etnaviv_iommu_unmap_gem function is responsible for unmapping memory regions previously mapped by the Etnaviv GPU driver. However, a vulnerability exists in this function that can be exploited by attackers.
Vulnerability Detail
The vulnerability in drm/etnaviv arises from a failure to check for reaped mappings in the etnaviv_iommu_unmap_gem function. This oversight can lead to a use-after-free scenario, where an attacker can manipulate freed memory to execute arbitrary code or cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet. It is important to note that this vulnerability has been fixed in Linux Kernel version v5.18.3 by commit 64f4edec081cb7c97c5e928529d0e1b0dbbffb83.
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
In conclusion, the vulnerability in drm/etnaviv's etnaviv_iommu_unmap_gem function can potentially lead to the execution of arbitrary code or denial-of-service attacks. It is crucial to update the Linux Kernel to version v5.18.3 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it has the potential to allow attackers to execute arbitrary code or cause a denial-of-service condition.
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 tool will provide real-time alerts for open-source vulnerabilities.
No specific workaround has been provided for this vulnerability. It is recommended to update to the fixed version of the Linux Kernel.
You can find more information about the fix in the commit 64f4edec081cb7c97c5e928529d0e1b0dbbffb83 in the Linux Kernel repository.
The discovery of this vulnerability was automated and reported by the Cloud Security Alliance's GSD Database.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
