ARM: exynos: Fix refcount leak in exynos_map_pmu
Summary
GSD-2022-1004737: ARM: exynos: Fix refcount leak in exynos_map_pmu. Affects Kernel versions >= fce9e5bb25264153f9f002eada41757118d25ba9, < f9b77a52937582a5b99a5a07e4ef1e2f48f87347. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The ARM Exynos kernel is a part of the Linux kernel and is specifically designed for ARM-based Exynos processors. It provides essential functionality for Exynos-based devices, including power management, memory management, and device drivers. However, a vulnerability has been discovered in the exynos_map_pmu function, which can lead to a refcount leak. This vulnerability was introduced in version v3.17 of the Linux kernel and affects Exynos-based devices running on this kernel version or later.
Vulnerability Detail
The vulnerability in the exynos_map_pmu function results in a refcount leak. This can lead to a variety of issues, including memory leaks, resource exhaustion, and potential privilege escalation attacks. An attacker could potentially exploit this vulnerability to gain unauthorized access or cause a denial of service. The vulnerability was fixed in version v5.4.202 of the Linux kernel by commit f9b77a52937582a5b99a5a07e4ef1e2f48f87347.
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 recommended to apply the fix as soon as possible by updating the Linux kernel.
Conclusion
The ARM Exynos kernel is vulnerable to a refcount leak in the exynos_map_pmu function. This vulnerability can lead to various security issues and should be addressed by updating the Linux kernel to version v5.4.202 or later. Users can check if their devices are affected using the Vulert Playground (https://vulert.com/scanner) and should apply the fix as soon as possible. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to memory leaks, resource exhaustion, and potential privilege escalation attacks.
Devices running on Linux kernel version v3.17 or later and using ARM-based Exynos processors are affected.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your application or device is affected by this vulnerability. Simply upload your package-lock.json file and it will provide real-time alerts for open-source vulnerabilities.
Yes, the vulnerability was fixed in version v5.4.202 of the Linux kernel by commit f9b77a52937582a5b99a5a07e4ef1e2f48f87347.
Unfortunately, there is no known workaround for this vulnerability. It is recommended to update the Linux kernel as soon as possible.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
