Refcount Leak in gamecube_rtc_read_offset_from_sram in Kernel
Summary
GSD-2022-1001109: rtc: gamecube: Fix refcount leak in gamecube_rtc_read_offset_from_sram. Affects Kernel versions >= 86559400b3ef9de93ba50523cffe767c35cd531a, < de66e4f28dfd11f954966c447b4430529ed040a2. 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 crucial component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities for the proper functioning of the system. The gamecube_rtc_read_offset_from_sram function is part of the Kernel's Real-Time Clock (RTC) subsystem, specifically designed for the GameCube platform. This function is responsible for reading the offset from the GameCube's SRAM (Static Random Access Memory) and has been found to have a refcount leak vulnerability.
Vulnerability Detail
The refcount leak vulnerability in gamecube_rtc_read_offset_from_sram allows an attacker to manipulate the reference count of the SRAM, potentially leading to memory corruption or resource exhaustion. By exploiting this vulnerability, an attacker could cause a denial-of-service (DoS) condition or execute arbitrary code with elevated privileges. The vulnerability was introduced in version v5.17 of the Linux Kernel and has been fixed in version v5.17.2.
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
As a temporary workaround, users can disable the gamecube_rtc_read_offset_from_sram function by modifying the Kernel configuration. However, this workaround may impact the functionality of the GameCube platform and is not recommended as a long-term solution. It is strongly advised to apply the official fix by updating the Kernel.
Conclusion
The refcount leak vulnerability in gamecube_rtc_read_offset_from_sram poses a risk of memory corruption and resource exhaustion. It is crucial to update the Linux Kernel to version v5.17.2 or later to mitigate this vulnerability. Applying the official fix ensures that the vulnerable code is replaced with the patched version, safeguarding the system from potential exploitation. For further support and assistance in vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can potentially lead to memory corruption or resource exhaustion, allowing an attacker to cause a denial-of-service (DoS) condition or execute arbitrary code with elevated privileges.
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, and Vulert will analyze it in real-time to identify any open-source vulnerabilities, including this one.
Yes, a temporary workaround is to disable the gamecube_rtc_read_offset_from_sram function by modifying the Kernel configuration. However, this is not recommended as a long-term solution, and it is advised to apply the official fix by updating the Kernel.
The vulnerability was introduced in version v5.17 of the Linux Kernel. All versions between v5.17 and v5.17.1 are affected. It has been fixed in version v5.17.2.
You can find more information about this vulnerability in the GSD-2022-1001109 entry of the GSD Database maintained by the Cloud Security Alliance. The source can be accessed at https://github.com/cloudsecurityalliance/gsd-database/blob/main/2022/1001xxx/GSD-2022-1001109.json.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
