ARM: versatile: Missing of_node_put in dcscb_init
Summary
GSD-2022-1003876: ARM: versatile: Add missing of_node_put in dcscb_init. Affects Kernel versions < a0fc05cd17617e63fc13ad0c01f3f0afd890d8ec. 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 versatile package is a versatile platform for running Linux on ARM-based systems. It provides support for various ARM processors and includes device drivers, system initialization code, and other essential components. The dcscb_init function is responsible for initializing the Device Configuration Space Control Block (DCSCB) for the versatile platform.
Vulnerability Detail
The vulnerability in the ARM versatile package arises from a missing of_node_put call in the dcscb_init function. This omission can lead to a reference count leak, potentially causing a resource exhaustion issue. An attacker may be able to exploit this vulnerability to exhaust system resources, resulting in a denial of service (DoS) condition. The vulnerability has been fixed in Linux Kernel version v4.19.247 by commit a0fc05cd17617e63fc13ad0c01f3f0afd890d8ec.
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 missing of_node_put in dcscb_init vulnerability in the ARM versatile package can potentially lead to a denial of service (DoS) condition. It is recommended to update the Linux Kernel to version v4.19.247 or later to fix this vulnerability. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to a denial of service (DoS) condition by exhausting system resources.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your manifest file (e.g., package-lock.json) and the playground will analyze it for vulnerabilities.
Yes, the vulnerability has been fixed in Linux Kernel version v4.19.247 by commit a0fc05cd17617e63fc13ad0c01f3f0afd890d8ec.
No specific workaround has been mentioned 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/2022/1003xxx/GSD-2022-1003876.json
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.