ARM: cns3xxx: Fix refcount leak in cns3xxx_init
Summary
GSD-2022-1004452: ARM: cns3xxx: Fix refcount leak in cns3xxx_init. Affects Kernel versions >= 415f59142d9d9dd023deaeb3b4dfc1aecdd3983c, < da3ee7cd2f15922ad88a7ca6deee2eafdc7cd214. 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 cns3xxx package is a component of the Linux Kernel. It provides support for the ARM Cortex-A9-based cns3xxx SoC family. The package includes various drivers and functionalities specific to this architecture. However, a vulnerability has been discovered in the cns3xxx_init function, which can lead to a refcount leak. This vulnerability was introduced in version v3.10 of the Linux Kernel and has been fixed in version v5.15.51.
Vulnerability Detail
The vulnerability in the cns3xxx_init function of the ARM cns3xxx package can result in a refcount leak. This can potentially lead to resource exhaustion or other memory-related issues. The refcount leak occurs due to improper handling of reference counting in certain scenarios. An attacker may be able to exploit this vulnerability to cause a denial-of-service condition or potentially execute arbitrary code. It is important to note that the impact and attack plausibility of this vulnerability have not been proven.
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
The ARM cns3xxx package in the Linux Kernel is vulnerable to a refcount leak in the cns3xxx_init function. This vulnerability can potentially lead to resource exhaustion or arbitrary code execution. It is crucial to update the Linux Kernel to version v5.15.51 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 can range from resource exhaustion to potential code execution. However, the actual impact and attack plausibility have not been proven.
You can use the Vulert Playground at Vulert Scanner to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will provide real-time alerts for open-source vulnerabilities, including this one.
At the moment, there are no known workarounds for this vulnerability. It is recommended to update the Linux Kernel to the fixed version.
There is no information available regarding exploitation of this vulnerability in the wild. However, it is always recommended to apply security updates promptly.
You can find more information about this vulnerability in the GSD-2022-1004452 entry of the GSD database. The source link is provided in the vulnerability details section.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
