LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50222: tty: vt: initialize unicode screen buffer

In the Linux kernel, the following vulnerability has been resolved: tty: vt: initialize unicode screen buffer syzbot reports kernel infoleak at vcs_read() [1], for buffer can be read immediately after resize operation. Initialize buffer using kzalloc(). ---------- #include <fcntl.h> #include <unistd.h> #include <sys/ioctl.h> #include <linux/fb.h> int main(int argc, char *argv[]) { struct fb_var_screeninfo var = { }; const int fb_fd = open("/dev/fb0", 3); ioctl(fb_fd, FBIOGET_VSCREENINFO, &var); var.yres = 0x21; ioctl(fb_fd, FBIOPUT_VSCREENINFO, &var); return read(open("/dev/vcsu", O_RDONLY), &var, sizeof(var)) == -1; } ----------

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2022-50222 is a Linux kernel information leak in the virtual terminal path. After a screen resize, a unicode screen buffer could be read before being initialized. The public record does not provide CVSS, CWE, or confirmed exploitation evidence, so urgency depends on where affected kernels run and who has local device access.

Executive priority

Treat as a kernel hygiene item with elevated priority for shared Linux systems. The available evidence does not justify emergency remote-exploitation response, but information leaks can support broader attack chains when local access exists.

Technical view

The issue is in Linux tty/vt handling around vcs_read(). The fix initializes the unicode screen buffer with kzalloc(), preventing stale kernel memory exposure after resize. The CVE record lists multiple stable kernel commit references and affected Linux version ranges, but does not describe remote attackability or privilege impact beyond the reported information leak.

Likely exposure

Exposure is most relevant on Linux systems running affected kernel builds, especially where local users or workloads can interact with virtual console or framebuffer-related device interfaces. Internet-facing exposure is not supported by the supplied sources.

Exploitation context

The source describes a syzbot-reported kernel infoleak and includes a local trigger pattern, but KEV is false and no cited source confirms active exploitation. Evidence supports a local information disclosure class, not a remote compromise claim.

Researcher notes

The public record is sparse: no CVSS, CWE, or vendor distribution mapping is supplied. Analysis should stay tied to the Linux stable commits and downstream advisories. Avoid overstating exploitability until privilege, namespace, and device-access preconditions are confirmed.

Mitigation direction

  • Update affected Linux kernels to builds containing the referenced stable fixes.
  • Check distribution advisories for vendor-specific fixed package versions.
  • Prioritize multi-user, shared, and sensitive workload hosts first.
  • Limit untrusted local access to relevant console or framebuffer devices where feasible.

Validation and detection

  • Inventory Linux kernel versions across servers, endpoints, and base images.
  • Compare installed kernels with vendor advisories and referenced stable commits.
  • Identify systems allowing untrusted local users or workloads device access.
  • Track remediation through normal kernel update and reboot completion evidence.
Prepared
Confidence
medium
Sources
9

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-50222 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
8Source 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
LinuxLinuxd8ae7242718738ee1bf9bfdd632d2a4b150fdd26, d8ae7242718738ee1bf9bfdd632d2a4b150fdd26, d8ae7242718738ee1bf9bfdd632d2a4b150fdd26, d8ae7242718738ee1bf9bfdd632d2a4b150fdd26, d8ae7242718738ee1bf9bfdd632d2a4b150fdd26, d8ae7242718738ee1bf9bfdd632d2a4b150fdd26, d8ae7242718738ee1bf9bfdd632d2a4b150fdd26unaffected
LinuxLinux4.19, 0, 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.