regmap: set debugfs_name to NULL after it is freed in Kernel
Summary
UVI-2021-1000463: regmap: set debugfs_name to NULL after it is freed. Affects Kernel versions >= 5b654b03007917f3f1015b2a5c288c1ea6ae8f65, < 2dc1554d5f0fdaf47cc5bea442b84b9226fea867. 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 Kernel is a crucial component of the Linux operating system that manages the system's resources and facilitates communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The regmap subsystem in the Kernel is responsible for managing register maps for various hardware devices. It allows device drivers to access and manipulate hardware registers in a unified manner. However, a vulnerability has been identified in the regmap subsystem that could potentially lead to security issues.
Vulnerability Detail
The vulnerability in the regmap subsystem involves not setting the debugfs_name variable to NULL after it is freed. This can result in a use-after-free scenario, where a reference to the freed debugfs_name variable is still accessible. An attacker could potentially exploit this vulnerability to execute arbitrary code or cause a denial-of-service condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v4.19.168 of the Linux Kernel and has been fixed in version v4.19.191.
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 specific workaround mentioned for this vulnerability.
Conclusion
The vulnerability in the regmap subsystem of the Kernel can potentially lead to security issues. It is recommended to update the Linux Kernel to version v4.19.191 or later to mitigate this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The impact of this vulnerability is not yet proven, but it could potentially allow an attacker to execute arbitrary code or cause a denial-of-service condition.
You can use Vulert's playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities without requiring access to the code or installation.
There is no known exploit for this vulnerability at the moment.
The recommended mitigation is to update the Linux Kernel to version v4.19.191 or later, which includes the fix for this vulnerability.
You can refer to the vulnerability details in the Open Source Vulnerability format at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2021/1000xxx/UVI-2021-1000463.json
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.
