LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50097: video: fbdev: s3fb: Check the size of screen before memset_io()

In the Linux kernel, the following vulnerability has been resolved: video: fbdev: s3fb: Check the size of screen before memset_io() In the function s3fb_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: [ 54.083733] BUG: unable to handle page fault for address: ffffc90003000000 [ 54.083742] #PF: supervisor write access in kernel mode [ 54.083744] #PF: error_code(0x0002) - not-present page [ 54.083760] RIP: 0010:memset_orig+0x33/0xb0 [ 54.083782] Call Trace: [ 54.083788] s3fb_set_par+0x1ec6/0x4040 [ 54.083806] fb_set_var+0x604/0xeb0 [ 54.083836] do_fb_ioctl+0x234/0x670 Fix the this by checking the value of 'screen_size' before memset_io().

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50097 is a Linux kernel bug in the s3fb framebuffer driver. Improper screen-size input can make the kernel write beyond the expected framebuffer area and crash with a kernel page fault. The sources do not provide CVSS, CWE, or business impact details.

Executive priority

Handle through normal kernel patch management unless the environment uses legacy S3 framebuffer hardware, exposed local shells, or broad framebuffer device access. Escalate if affected systems are multi-user or difficult to patch.

Technical view

In s3fb_set_par(), screen_size is derived from user input. If it exceeds info->screen_size, memset_io() can write beyond the valid mapped screen memory and trigger a supervisor-mode page fault. The kernel fix adds a size check before memset_io().

Likely exposure

Exposure appears limited to Linux systems using the fbdev s3fb driver or relevant framebuffer path. Systems without this driver, without framebuffer device access, or running kernels with the stable fix are less likely to be affected.

Exploitation context

The source shows a kernel crash path through fb_set_var and do_fb_ioctl. There is no cited evidence of active exploitation, public weaponization, privilege escalation, or remote reachability. KEV status is false in the provided bundle.

Researcher notes

Evidence is narrow: the bundle documents the bug, crash trace, affected Linux ranges, and stable commits. It does not establish exploitability beyond denial-of-service, attacker prerequisites, or impact on confidentiality or integrity.

Mitigation direction

  • Update to a vendor kernel containing the referenced stable fix.
  • Check distribution advisories for backported fixes before assuming version exposure.
  • Disable or avoid loading s3fb where it is not operationally required.
  • Restrict access to framebuffer devices to trusted users only.

Validation and detection

  • Inventory Linux kernel versions on systems with framebuffer support.
  • Confirm whether s3fb is built, loaded, or needed on affected hosts.
  • Verify vendor package changelogs or source contain the referenced fix.
  • Review device permissions for /dev/fb* on multi-user systems.
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-50097 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
LinuxLinuxa268422de8bf1b4c0cb97987b6c329c9f6a3da4b, a268422de8bf1b4c0cb97987b6c329c9f6a3da4b, a268422de8bf1b4c0cb97987b6c329c9f6a3da4b, a268422de8bf1b4c0cb97987b6c329c9f6a3da4b, a268422de8bf1b4c0cb97987b6c329c9f6a3da4b, a268422de8bf1b4c0cb97987b6c329c9f6a3da4b, a268422de8bf1b4c0cb97987b6c329c9f6a3da4b, a268422de8bf1b4c0cb97987b6c329c9f6a3da4bunaffected
LinuxLinux2.6.21, 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.