Skip to content
CVE Tracker
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API documentationPage
  • MCP serverPage
  • Data sourcesPage
  • ChangelogPage
  • AboutPage
  • How it's builtPage
Back

CVE-2022-50102

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

Medium5.5EPSS 0.19%
Published
Updated
Reserved
Assigned by
Linux

Description

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.

Scores

CVSS scores of CVE-2022-50102, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.19% · top 91% of all CVEs (6 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Weakness

Affected products

  • Linux · Linux

    • affected 681e14730c73cc2c71af282c001de6bc71c22f00 – < 76b3f0a0b56e53a960a14624a0f48b3d94b5e7e7
    • affected 681e14730c73cc2c71af282c001de6bc71c22f00 – < b9a66f23612b84617e04412169e155a4b92f632d
    • affected 681e14730c73cc2c71af282c001de6bc71c22f00 – < a249e1b89ca25e1c34bdf96154e3f6224a91a9af
    • affected 681e14730c73cc2c71af282c001de6bc71c22f00 – < 0288fa799e273b08839037499d704dc7bdc13e9a
    • affected 681e14730c73cc2c71af282c001de6bc71c22f00 – < 236c1502520b7b08955467ec2e50b3232e34f1f9
    • affected 681e14730c73cc2c71af282c001de6bc71c22f00 – < 9ebc5031958c1f3a2795e4533b4091d77c738d14
    • affected 681e14730c73cc2c71af282c001de6bc71c22f00 – < 15661642511b2b192077684a89f42a8d95d54286
    • affected 681e14730c73cc2c71af282c001de6bc71c22f00 – < 2f1c4523f7a3aaabe7e53d3ebd378292947e95c8
  • Linux · Linux

    • affected 2.6.22
    • unaffected < 2.6.22
    • unaffected 4.14.291 – ≤ 4.14.*
    • unaffected 4.19.256 – ≤ 4.19.*
    • unaffected 5.4.211 – ≤ 5.4.*
    • unaffected 5.10.137 – ≤ 5.10.*
    • unaffected 5.15.61 – ≤ 5.15.*
    • unaffected 5.18.18 – ≤ 5.18.*
    • unaffected 5.19.2 – ≤ 5.19.*
    • unaffected 6.0 – ≤ *

References (8)

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2022-50102 badge
[![CVE-2022-50102](https://trackcve.app/badge/CVE-2022-50102.svg)](https://trackcve.app/cve/CVE-2022-50102)

Record last updated .