CVE-2022-50102

published 18 Jun 2025 · updated 11 May 2026

video: fbdev: arkfb: Fix a divide-by-zero bug in ark_set_pixclock()

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 0288fa799e273b08839037499d704dc7bdc13e9a, Kernel 15661642511b2b192077684a89f42a8d95d54286, Kernel 236c1502520b7b08955467ec2e50b3232e34f1f9 and 5 more.

In the Linux kernel, the following vulnerability has been resolved: video: fbdev: arkfb: Fix a divide-by-zero bug in ark_set_pixclock() Since the user can control the arguments of the ioctl() from the user space, under special arguments that may result in a divide-by-zero bug in: drivers/video/fbdev/arkfb.c:784: ark_set_pixclock(info, (hdiv * info->var.pixclock) / hmul); with hdiv=1, pixclock=1 and hmul=2 you end up with (1*1)/2 = (int) 0. and then in: drivers/video/fbdev/arkfb.c:504: rv = dac_set_freq(par->dac, 0, 1000000000 / pixclock); we'll get a division-by-zero. The following log can reveal it: divide error: 0000 [#1] PREEMPT SMP KASAN PTI RIP: 0010:ark_set_pixclock drivers/video/fbdev/arkfb.c:504 [inline] RIP: 0010:arkfb_set_par+0x10fc/0x24c0 drivers/video/fbdev/arkfb.c:784 Call Trace: fb_set_var+0x604/0xeb0 drivers/video/fbdev/core/fbmem.c:1034 do_fb_ioctl+0x234/0x670 drivers/video/fbdev/core/fbmem.c:1110 fb_ioctl+0xdd/0x130 drivers/video/fbdev/core/fbmem.c:1189 Fix this by checking the argument of ark_set_pixclock() first.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel=2.6.22, >=681e14730c73cc2c71af282c001de6bc71c22f00 <0288fa799e273b08839037499d704dc7bdc13e9a, >=681e14730c73cc2c71af282c001de6bc71c22f00 <15661642511b2b192077684a89f42a8d95d54286, >=681e14730c73cc2c71af282c001de6bc71c22f00 <236c1502520b7b08955467ec2e50b3232e34f1f9, >=681e14730c73cc2c71af282c001de6bc71c22f00 <2f1c4523f7a3aaabe7e53d3ebd378292947e95c8, >=681e14730c73cc2c71af282c001de6bc71c22f00 <76b3f0a0b56e53a960a14624a0f48b3d94b5e7e7, >=681e14730c73cc2c71af282c001de6bc71c22f00 <9ebc5031958c1f3a2795e4533b4091d77c738d14, >=681e14730c73cc2c71af282c001de6bc71c22f00 <a249e1b89ca25e1c34bdf96154e3f6224a91a9af, >=681e14730c73cc2c71af282c001de6bc71c22f00 <b9a66f23612b84617e04412169e155a4b92f632d0288fa799e273b08839037499d704dc7bdc13e9a, 15661642511b2b192077684a89f42a8d95d54286, 236c1502520b7b08955467ec2e50b3232e34f1f9, 2f1c4523f7a3aaabe7e53d3ebd378292947e95c8, 76b3f0a0b56e53a960a14624a0f48b3d94b5e7e7, 9ebc5031958c1f3a2795e4533b4091d77c738d14, a249e1b89ca25e1c34bdf96154e3f6224a91a9af, b9a66f23612b84617e04412169e155a4b92f632d

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2022-50102 severity on Zeptric[![CVE-2022-50102](https://zeptric.io/badge/cve/CVE-2022-50102.svg)](https://zeptric.io/cve/CVE-2022-50102)