LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50099: video: fbdev: arkfb: Check the size of screen before memset_io()

In the Linux kernel, the following vulnerability has been resolved: video: fbdev: arkfb: Check the size of screen before memset_io() In the function arkfb_set_par(), the value of 'screen_size' is calculated by the user input. If the user provides the improper value, the value of 'screen_size' may larger than 'info->screen_size', which may cause the following bug: [ 659.399066] BUG: unable to handle page fault for address: ffffc90003000000 [ 659.399077] #PF: supervisor write access in kernel mode [ 659.399079] #PF: error_code(0x0002) - not-present page [ 659.399094] RIP: 0010:memset_orig+0x33/0xb0 [ 659.399116] Call Trace: [ 659.399122] arkfb_set_par+0x143f/0x24c0 [ 659.399130] fb_set_var+0x604/0xeb0 [ 659.399161] do_fb_ioctl+0x234/0x670 [ 659.399189] fb_ioctl+0xdd/0x130 Fix the this by checking the value of 'screen_size' before memset_io().

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-50099 is a Linux kernel flaw in the arkfb framebuffer driver. Improper screen size input can make the kernel write beyond the expected framebuffer area and hit a page fault. The source evidence points to potential local system instability, not confirmed remote compromise or active exploitation.

Executive priority

Treat this as a targeted kernel maintenance issue. Prioritize systems with framebuffer hardware, local multi-user access, or embedded/console workloads. It is not currently supported as an internet-scale emergency by the provided evidence.

Technical view

In arkfb_set_par(), screen_size is calculated from user-controlled framebuffer settings. If it exceeds info->screen_size, memset_io() can write outside the valid mapped screen region, triggering a supervisor-mode page fault. The fix adds a screen_size check before memset_io().

Likely exposure

Exposure is most relevant on Linux systems using or enabling the arkfb framebuffer driver, especially where local users or processes can reach framebuffer ioctls. Generic servers without this driver or device access are less likely exposed.

Exploitation context

The bundle does not report KEV listing, active exploitation, public exploit use, or remote attack evidence. The described path is local interaction through framebuffer ioctl handling and demonstrates a kernel crash condition.

Researcher notes

The CVE record identifies a bounds-checking failure before memset_io() in video/fbdev/arkfb. Evidence supports a kernel fault from oversized calculated screen_size, but does not establish privilege escalation, information disclosure, or exploitation in the wild.

Mitigation direction

  • Apply Linux vendor kernel updates containing the referenced arkfb fix commits.
  • Confirm distribution backports if kernel versions differ from upstream stable numbers.
  • If immediate patching is delayed, check vendor guidance for supported temporary mitigations.
  • Reduce unnecessary local access to framebuffer devices where operationally feasible.

Validation and detection

  • Inventory Linux kernels and compare against affected versions listed in the CVE bundle.
  • Check whether the arkfb driver is built, loaded, or available on target systems.
  • Verify vendor kernel changelogs or source include the screen_size check before memset_io().
  • Review kernel logs for arkfb_set_par, fb_ioctl, or similar page fault traces.
Prepared
Confidence
medium
Sources
10

Public sources used

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-50099 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.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LinuxLinux681e14730c73cc2c71af282c001de6bc71c22f00, 681e14730c73cc2c71af282c001de6bc71c22f00, 681e14730c73cc2c71af282c001de6bc71c22f00, 681e14730c73cc2c71af282c001de6bc71c22f00, 681e14730c73cc2c71af282c001de6bc71c22f00, 681e14730c73cc2c71af282c001de6bc71c22f00, 681e14730c73cc2c71af282c001de6bc71c22f00, 681e14730c73cc2c71af282c001de6bc71c22f00unaffected
LinuxLinux2.6.22, 0, 4.14.291, 4.19.256, 5.4.211, 5.10.137, 5.15.61, 5.18.18, 5.19.2, 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.