LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50010: video: fbdev: i740fb: Check the argument of i740_calc_vclk()

In the Linux kernel, the following vulnerability has been resolved: video: fbdev: i740fb: Check the argument of i740_calc_vclk() 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. If the user provides an improper 'pixclock' value that makes the argumet of i740_calc_vclk() less than 'I740_RFREQ_FIX', it will cause a divide-by-zero bug in: drivers/video/fbdev/i740fb.c:353 p_best = min(15, ilog2(I740_MAX_VCO_FREQ / (freq / I740_RFREQ_FIX))); The following log can reveal it: divide error: 0000 [#1] PREEMPT SMP KASAN PTI RIP: 0010:i740_calc_vclk drivers/video/fbdev/i740fb.c:353 [inline] RIP: 0010:i740fb_decode_var drivers/video/fbdev/i740fb.c:646 [inline] RIP: 0010:i740fb_set_par+0x163f/0x3b70 drivers/video/fbdev/i740fb.c:742 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 i740_calc_vclk() first.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel bug in the i740 framebuffer driver. A local user who can reach the framebuffer ioctl interface may be able to trigger a divide-by-zero kernel fault. The most likely business impact is local denial of service on systems using this legacy display driver.

Executive priority

Treat as a targeted kernel hardening issue, not an emergency remote compromise. Prioritize patching systems that expose framebuffer devices to local users, shared workstations, labs, or kiosk-like environments.

Technical view

The flaw is in drivers/video/fbdev/i740fb.c. User-controlled ioctl input can provide an improper pixclock value, causing i740_calc_vclk() to divide by zero during framebuffer mode setting. Kernel stable commits add argument validation before the calculation.

Likely exposure

Exposure appears limited to Linux systems with affected kernel versions and the i740fb framebuffer driver present and reachable from user space. The source bundle does not identify broad default exposure, specific distributions, containers, or remote attack paths.

Exploitation context

The provided sources describe user-space control through ioctl and a kernel divide error trace. They do not cite active exploitation, public exploit availability, or CISA KEV listing; KEV is marked false.

Researcher notes

Evidence supports a local ioctl-triggered divide-by-zero in i740fb. The bundle provides affected Linux version data and fix commits, but no CVSS, CWE, distro mapping, exploit confirmation, or remote vector evidence.

Mitigation direction

  • Apply a vendor kernel update containing the referenced stable fixes.
  • Confirm the fix validates i740_calc_vclk() input before calculation.
  • If no update is available, check distribution vendor guidance.
  • Limit framebuffer device access to trusted users where operationally feasible.

Validation and detection

  • Inventory kernels against vendor advisories and the referenced stable commits.
  • Check whether i740fb is built, loaded, or deployable on affected hosts.
  • Review permissions and usage of framebuffer device nodes.
  • Track remediation through standard kernel patch compliance reporting.
Prepared
Confidence
medium
Sources
10

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2022-50010 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
3Timeline events
0ADP providers
9Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux5350c65f4f15bbc111ffa629130d3f32cdd4ccf6, 5350c65f4f15bbc111ffa629130d3f32cdd4ccf6, 5350c65f4f15bbc111ffa629130d3f32cdd4ccf6, 5350c65f4f15bbc111ffa629130d3f32cdd4ccf6, 5350c65f4f15bbc111ffa629130d3f32cdd4ccf6, 5350c65f4f15bbc111ffa629130d3f32cdd4ccf6, 5350c65f4f15bbc111ffa629130d3f32cdd4ccf6, 5350c65f4f15bbc111ffa629130d3f32cdd4ccf6unaffected
LinuxLinux3.4, 0, 4.9.326, 4.14.291, 4.19.256, 5.4.211, 5.10.138, 5.15.63, 5.19.4, 6.0affected
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.