Refcount Leaks in ax25_cb_del() Function in Kernel
Summary
GSD-2022-1001825: ax25: Fix refcount leaks caused by ax25_cb_del(). Affects Kernel versions >= 9af0fd5c4453a44c692be0cbb3724859b75d739b, < 452ae92b99062d2f6a34324eaf705a3b7eac9f8b. 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 acts as a bridge between the hardware and software layers. It provides essential services, such as process management, memory management, and device drivers. The ax25 module in the Kernel is responsible for implementing the AX.25 protocol, which is used for packet radio communication. This vulnerability affects the ax25_cb_del() function in the ax25 module.
Vulnerability Detail
The ax25_cb_del() function in the ax25 module of the Kernel has refcount leaks, which can lead to memory leaks and potential resource exhaustion. This vulnerability can be exploited by an attacker to cause a denial-of-service (DoS) condition or potentially execute arbitrary code with elevated privileges. The issue arises when the ax25_cb_del() function fails to properly release the reference count of an AX.25 control block, resulting in a memory leak. This can be abused by an attacker to exhaust system resources and disrupt normal system operation.
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 workaround, users can disable the ax25 module if it is not required for their system. This can be achieved by blacklisting the module or removing it from the Kernel configuration. However, this workaround should only be considered if the ax25 module is not essential for the system's functionality.
Conclusion
The refcount leaks in the ax25_cb_del() function of the Kernel's ax25 module can lead to memory leaks and potential resource exhaustion. It is crucial to update the Linux Kernel to version v5.15.35 or later to mitigate this vulnerability. Users can also consider disabling the ax25 module if it is not necessary for their system. For further support on vulnerability remediation, you can reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can lead to memory leaks and potential resource exhaustion, resulting in a denial-of-service (DoS) condition. It may also allow an attacker to execute arbitrary code with elevated privileges.
You can use Vulert's playground at Vulert Scanner to check if your system is affected by this vulnerability. Vulert uses a manifest file like package-lock.json to monitor and alert in real-time for open-source vulnerabilities.
Yes, users can disable the ax25 module if it is not required for their system. This can be achieved by blacklisting the module or removing it from the Kernel configuration.
The recommended solution is to update the Linux Kernel to version v5.15.35 or later, which includes the fix for this vulnerability.
You can find more information about this vulnerability in the Open Source Vulnerability Database (OSVDB) entry with ID GSD-2022-1001825.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
