Out of Bounds Access Vulnerability in kyber
Summary
GSD-2021-1000317: kyber: fix out of bounds access when preempted. Affects Kernel versions >= a6088845c2bf754d6cb2572b484180680b037804, < 54dbe2d2c1fcabf650c7a8b747601da355cd7f9f. 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 kyber vulnerability affects the Linux Kernel, specifically versions 4.18 to 5.10.38. The Linux Kernel is the core component of the Linux operating system, responsible for managing system resources and providing an interface for software to interact with the hardware. kyber is a block I/O scheduler used in the Linux Kernel to optimize the order in which I/O requests are processed. This vulnerability allows for out of bounds access when preempted, potentially leading to memory corruption or privilege escalation.
Vulnerability Detail
The kyber vulnerability arises from an out of bounds access issue when the scheduler is preempted. This can occur when multiple processes are competing for system resources, and the scheduler is interrupted to switch to a different process. The out of bounds access can result in memory corruption or privilege escalation, potentially allowing an attacker to execute arbitrary code or gain elevated privileges. The vulnerability was introduced in Linux Kernel version 4.18 and is fixed in version 5.10.38.
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 available for this vulnerability. It is recommended to apply the fix by updating the Linux Kernel to the latest version.
Conclusion
The kyber vulnerability in the Linux Kernel can lead to memory corruption or privilege escalation. It is crucial to update the Linux Kernel to version 5.10.38 or later to mitigate the risk of exploitation. For additional support, please reach out to DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The kyber vulnerability can potentially lead to memory corruption or privilege escalation. This can allow an attacker to execute arbitrary code or gain elevated privileges on the affected system.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by the kyber vulnerability. Simply upload your package-lock.json file and Vulert will analyze it for any open-source vulnerabilities, including the kyber vulnerability.
At the time of this report, there are no known exploits for the kyber vulnerability. However, it is important to apply the fix as soon as possible to mitigate the risk of potential exploitation.
No, this vulnerability requires local access to the affected system in order to exploit it. Remote exploitation is not possible.
For further support on vulnerability remediation, you can contact info@devnack.com. They can provide assistance and guidance on fixing the kyber vulnerability.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.