fbdev: savage: Error out if pixclock equals zero
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 · < bc3c2e58d73b28b9a8789fca84778ee165a72d13| No fix yet |
| Linux Linux |
|
|
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 savagefb_decode_var(), but it is not checked properly in savagefb_probe(). Fix this by checking whether pixclock is zero in the function savagefb_check_var() before info->var.pixclock is used as the divisor.
This is similar to CVE-2022-3061 in i740fb which was fixed by commit 15cf0b8.
From the CVE record · Linux
The Linux kernel's savage framebuffer driver does not properly reject a zero pixclock before using it as a divisor. A local userspace program can pass that value through the ioctl interface and trigger a divide-by-zero error; authentication requirements are not specified.
Engineers running Linux kernels with the savage framebuffer driver should check their exposure; affected versions are not specified.