Divide by Zero Vulnerability in Kernel
Summary
GSD-2022-1002216: video: fbdev: cirrusfb: check pixclock to avoid divide by zero. Affects Kernel versions < 53a2088a396cfa1da92690a1da289634cd73bf0d. 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 functionalities such as device drivers, memory management, and process scheduling. The vulnerability in question affects the Kernel's video subsystem, specifically the fbdev driver for Cirrus Logic graphics cards. This driver is responsible for managing the framebuffer device and enabling graphical output on the screen.
Vulnerability Detail
The vulnerability arises from a lack of proper validation in the Cirrus Logic framebuffer driver (cirrusfb) when handling the pixel clock (pixclock) parameter. By exploiting this flaw, an attacker could trigger a divide by zero error, leading to a system crash or potential privilege escalation. The vulnerability has the potential to impact the stability and security of the affected system.
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 use of the cirrusfb driver if it is not essential for their system. This can be achieved by blacklisting the driver module or configuring the system to use an alternative framebuffer driver. However, this workaround may result in the loss of graphical output for Cirrus Logic graphics cards.
Conclusion
The divide by zero vulnerability in the Kernel's cirrusfb driver can have severe consequences, including system crashes and potential privilege escalation. It is crucial to update the Linux Kernel to version v5.4.189 or later, which includes the necessary fix. Users can also utilize the Vulert Playground at https://vulert.com/scanner to check if their system is affected by this vulnerability. For further assistance and support in addressing this vulnerability, please contact DevNack.com.
See every vulnerability recorded for Kernel →
FAQ
The vulnerability can lead to a system crash or potential privilege escalation, compromising the stability and security of the affected system.
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 to the playground, and it will analyze and alert you in real-time if the vulnerability is present.
No, the vulnerability is fixed in Linux Kernel version v5.4.189 and later. It is recommended to update to a version that includes the fix.
Yes, as a temporary workaround, you can disable the cirrusfb driver if it is not essential for your system. However, this may result in the loss of graphical output for Cirrus Logic graphics cards.
You can find more details about the fix in the commit 53a2088a396cfa1da92690a1da289634cd73bf0d in the Linux Kernel repository at https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/.
Related vulnerabilities
Recent vulnerabilities recorded for Kernel.
