Out-of-bounds bug in ngene_command_config_free_buf() in Kernel
Summary
GSD-2021-1001236: media: ngene: Fix out-of-bounds bug in ngene_command_config_free_buf(). Affects Kernel versions >= dae52d009fc950b5c209260d50fcc000f5becd3c, < e991457afdcb5f4dbc5bc9d79eaf775be33e7092. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The Kernel is a critical component of the Linux operating system that manages system resources and facilitates communication between hardware and software. It provides essential functionalities such as process management, memory management, and device drivers. The ngene subsystem within the Kernel is responsible for supporting the Next Generation Network Encryption (NGENE) hardware. This vulnerability affects the ngene_command_config_free_buf() function within the ngene subsystem.
Vulnerability Detail
The ngene_command_config_free_buf() function in the ngene subsystem of the Kernel has an out-of-bounds bug. This vulnerability allows an attacker to manipulate memory beyond the intended boundaries, potentially leading to memory corruption, crashes, or arbitrary code execution. The bug was introduced in version v2.6.34 of the Kernel and was fixed in version v5.10.54.
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 known workaround for this vulnerability. It is essential to update the Kernel to the fixed version.
Conclusion
The out-of-bounds bug in ngene_command_config_free_buf() within the Kernel's ngene subsystem can lead to memory corruption and potential code execution. It is crucial to update the Kernel to version v5.10.54 or later to mitigate this vulnerability. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
This vulnerability can potentially be exploited by an attacker to manipulate memory and execute arbitrary code, leading to system crashes or unauthorized access to sensitive information.
You can use the Vulert Playground (https://vulert.com/scanner) to check if your system is affected by this vulnerability. Simply upload your package-lock.json file to the playground, and it will analyze the dependencies and alert you if any known vulnerabilities are present.
No, only versions starting from v2.6.34 up to v5.10.53 are affected. The vulnerability has been fixed in version v5.10.54.
No, the recommended solution is to update to the fixed version of the Kernel.
The exact attack vector and exploitability of this vulnerability have not been proven. However, it is always recommended to apply security updates promptly to mitigate potential risks.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
