ARM: exynos: Fix refcount leak in exynos_map_pmu
Summary
GSD-2022-1004823: ARM: exynos: Fix refcount leak in exynos_map_pmu. Affects Kernel versions >= fce9e5bb25264153f9f002eada41757118d25ba9, < 7571bcecf01b69f0d3ec60ca41ce5d4c75411a4a. 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 ARM Exynos kernel module is responsible for managing the Exynos processor on ARM-based devices. It provides various functionalities and optimizations specific to the Exynos architecture. However, a vulnerability has been discovered in the module that can lead to a refcount leak in the exynos_map_pmu function.
Vulnerability Detail
The vulnerability in the exynos_map_pmu function can result in a refcount leak, potentially leading to resource exhaustion or other memory-related issues. This vulnerability was introduced in version v3.17 of the Linux Kernel and has been fixed in version v4.19.250. An attacker may be able to exploit this vulnerability to cause a denial-of-service condition or potentially execute arbitrary code.
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
No specific workaround has been provided for this vulnerability.
Conclusion
In conclusion, the ARM Exynos kernel module is vulnerable to a refcount leak in the exynos_map_pmu function. This vulnerability can potentially lead to resource exhaustion or other memory-related issues. It is recommended to update the Linux Kernel to version v4.19.250 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially lead to resource exhaustion or other memory-related issues. An attacker may be able to cause a denial-of-service condition or execute arbitrary code.
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 playground will analyze it for any open-source vulnerabilities, including this one.
At the time of this report, there is no known exploit for this vulnerability. However, it is always recommended to apply security patches and updates to mitigate any potential risks.
The recommended solution is to update the Linux Kernel to the latest version. However, if updating is not feasible, you can consider implementing additional security measures, such as network segmentation and access controls, to minimize the risk of exploitation.
The discovery of this vulnerability is credited to the security research community. The specific researcher or organization responsible for its discovery is not mentioned in the available information.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
