CVE-2024-26778: fbdev: savage: Error out if pixclock equals zero
In the Linux kernel, the following vulnerability has been resolved:
fbdev: savage: Error out if pixclock equals zero
The userspace program could pass any values to the driver through ioctl() interface. If the driver doesn't check the value of pixclock, it may cause divide-by-zero error.
Although pixclock is checked in savagefbdecodevar(), but it is not checked properly in savagefbprobe(). Fix this by checking whether pixclock is zero in the function savagefbcheckvar() before info->var.pixclock is used as the divisor.
This is similar to CVE-2022-3061 in i740fb which was fixed by commit 15cf0b8.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
debian/linuxto a version that resolves this vulnerability.Fixed in 5.10.223-1Fixed in 5.10.234-1Fixed in 6.1.129-1Fixed in 6.1.135-1Fixed in 6.12.25-1 - Upgrade
Upgrade
Linux kernel fbdev savageto a version that resolves this vulnerability.Patch 15cf0b8
Event History
Frequently Asked Questions
What is the severity of CVE-2024-26778?
CVE-2024-26778 has been classified as a security vulnerability that can lead to potential system crashes due to a divide-by-zero error.
How do I fix CVE-2024-26778?
To resolve CVE-2024-26778, users should upgrade to the fixed versions of the Linux kernel available, including versions 5.10.223-1, 5.10.226-1, 6.1.119-1, 6.1.123-1, 6.12.10-1, and 6.12.11-1.
Which Linux distributions are affected by CVE-2024-26778?
CVE-2024-26778 primarily affects Debian-based Linux distributions that utilize the vulnerable versions of the Linux kernel.
What happens if CVE-2024-26778 is exploited?
If exploited, CVE-2024-26778 can cause the userspace program to crash, potentially disrupting services and impacting system stability.
Is there a workaround for CVE-2024-26778?
Currently, the best course of action is to upgrade the affected kernel versions, as no official workarounds have been published.