Refcount Leak in aspeed_adc_set_trim_data in Kernel
Summary
GSD-2022-1004253: iio: adc: aspeed: Fix refcount leak in aspeed_adc_set_trim_data. Affects Kernel versions >= d0a4c17b40736b368f1f26602ad162e24b4108e7, < 9664491db50a84be92696c8fad2c3b49a7a5f36f. 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 Kernel is a critical component of the Linux operating system that provides core functionalities and interfaces with hardware devices. It acts as a bridge between software applications and the computer's hardware. The aspeed_adc_set_trim_data function is part of the iio (Industrial I/O) subsystem in the Kernel, specifically designed for handling analog-to-digital converters (ADCs) on ASPEED SoCs. ADCs are essential for converting analog signals from sensors or other devices into digital data that can be processed by the system. However, a vulnerability has been identified in the aspeed_adc_set_trim_data function, which can lead to a refcount leak.
Vulnerability Detail
The vulnerability in aspeed_adc_set_trim_data arises from a refcount leak. When certain conditions are met, the function fails to properly release a reference count, leading to a resource leak. An attacker could potentially exploit this vulnerability to exhaust system resources, resulting in a denial-of-service (DoS) condition. The impact and attack plausibility of this vulnerability have not been proven yet. The vulnerability was introduced in version v5.16 of the Linux Kernel and has been fixed in version v5.18.8.
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 refcount leak vulnerability in aspeed_adc_set_trim_data can potentially lead to a denial-of-service (DoS) condition. It is crucial to update the Linux Kernel to version v5.18.8 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
The impact of this vulnerability is not yet proven. However, it could 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 Vulert will analyze it for any open-source vulnerabilities, including this one.
No known exploit for this vulnerability has been reported at this time.
The recommended approach is to update the Kernel to the fixed version. However, if updating is not immediately feasible, it is advisable to follow general security best practices, such as restricting access to vulnerable systems and implementing network-level protections.
For more details about this vulnerability, you can refer to the source link provided in the database_specific section of the vulnerability details.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
