Vulnerability in mips_cdmm_phys_base in Kernel
Summary
GSD-2022-1001210: mips: cdmm: Fix refcount leak in mips_cdmm_phys_base. Affects Kernel versions >= 2121aa3e2312ccc1d6299154dc4f07a6ab8beee2, < 721ab4be20d4448dd04c2cc8ed99cd4f3e45f765. 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 fundamental component of the Linux operating system that manages core system functions and provides an interface between hardware and software. It is responsible for memory management, process scheduling, device drivers, and other essential tasks. The vulnerability in mips_cdmm_phys_base affects the Kernel's MIPS architecture. MIPS (Microprocessor without Interlocked Pipeline Stages) is a reduced instruction set computer (RISC) architecture commonly used in embedded systems and networking devices.
Vulnerability Detail
The vulnerability in mips_cdmm_phys_base results in a refcount leak. This can lead to resource exhaustion and potential denial-of-service (DoS) attacks. The issue was introduced in version v5.9 of the Linux Kernel and was fixed in version v5.17.2. The vulnerability allows an attacker to manipulate the refcount, causing it to leak and potentially exhaust system resources. The impact and attack plausibility of this vulnerability have not been proven yet.
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 vulnerability in mips_cdmm_phys_base in the Kernel can lead to resource exhaustion and potential denial-of-service attacks. It is crucial to update the Linux Kernel to version v5.17.2 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to resource exhaustion and potential denial-of-service (DoS) attacks.
You can use Vulert's playground (https://vulert.com/scanner) to check if your application 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.
At the time of this report, there is no known exploit for this vulnerability.
The recommended mitigation is to update the Linux Kernel to the latest version that includes the fix for this vulnerability.
The remote exploitability of this vulnerability has not been determined yet.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.