fbdev: savage: Handle err return when savagefb_check_var failed
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ bc3c2e58d73b28b9a8789fca84778ee165a72d13 · < b8385ff814ca4cb7e63789841e6ec2a14c73e1e8| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
fbdev: savage: Handle err return when savagefb_check_var failed
The commit 04e5eac8f3ab("fbdev: savage: Error out if pixclock equals zero") checks the value of pixclock to avoid divide-by-zero error. However the function savagefb_probe doesn't handle the error return of savagefb_check_var. When pixclock is 0, it will cause divide-by-zero error.
From the CVE record · Linux
The Linux kernel's savage framebuffer driver does not handle an error returned by savagefb_check_var during probing. If pixclock is zero, a divide-by-zero error can occur. The input does not specify how an attacker could trigger this condition or whether authentication or user interaction is required.
Teams running the Linux kernel with the savage framebuffer driver should check their deployments; affected versions are not specified.