LiveActive security incident?Get immediate response
CVE Record

CVE-2022-50221: drm/fb-helper: Fix out-of-bounds access

In the Linux kernel, the following vulnerability has been resolved: drm/fb-helper: Fix out-of-bounds access Clip memory range to screen-buffer size to avoid out-of-bounds access in fbdev deferred I/O's damage handling. Fbdev's deferred I/O can only track pages. From the range of pages, the damage handler computes the clipping rectangle for the display update. If the fbdev screen buffer ends near the beginning of a page, that page could contain more scanlines. The damage handler would then track these non-existing scanlines as dirty and provoke an out-of-bounds access during the screen update. Hence, clip the maximum memory range to the size of the screen buffer. While at it, rename the variables min/max to min_off/max_off in drm_fb_helper_deferred_io(). This avoids confusion with the macros of the same name.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This is a Linux kernel graphics bug where deferred framebuffer updates can mark screen lines that do not exist. That can cause out-of-bounds memory access during display update handling. The source bundle does not provide a CVSS score, exploit evidence, or business impact details.

Executive priority

Schedule remediation through normal kernel patch governance unless local exposure is broad or systems are safety-critical. There is no cited evidence of active exploitation, but kernel memory bugs can carry elevated operational risk.

Technical view

The issue is in drm/fb-helper deferred I/O damage handling. Because fbdev tracks dirty memory by page, a screen buffer ending near the start of a page could make the handler calculate non-existent scanlines. The resolved fix clips the tracked memory range to the screen-buffer size.

Likely exposure

Exposure is likely limited to Linux kernels and configurations using the affected DRM fb-helper/fbdev deferred I/O path. The source lists Linux kernel version data including 5.18, 5.19.2, and 6.0, but the provided bundle does not fully clarify exact deployed-version ranges.

Exploitation context

The provided sources do not report active exploitation, public exploit availability, or KEV listing. Treat this as a kernel memory-safety issue requiring version validation, not as confirmed exploited-in-the-wild activity.

Researcher notes

The key validation question is whether the affected deferred I/O damage path is reachable in the target kernel build and runtime configuration. The source bundle names the fix behavior but provides no crash primitive, exploitability assessment, CVSS, or confirmed attack scenario.

Mitigation direction

  • Check vendor or distribution advisories for fixed kernel packages.
  • Prioritize updates on systems using framebuffer or DRM display paths.
  • Track the two referenced stable kernel commits as fix evidence.
  • Avoid inventing local workarounds without vendor confirmation.

Validation and detection

  • Inventory Linux kernel versions across servers, appliances, and endpoints.
  • Identify systems using affected fbdev or DRM framebuffer functionality.
  • Compare deployed kernels against vendor-fixed releases or referenced stable commits.
  • Document any systems that cannot be updated promptly.
Prepared
Confidence
medium
Sources
4

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-50221 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
3Source 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
LinuxLinux67b723f5b74254d27962b1b59bddfee1584575ff, 67b723f5b74254d27962b1b59bddfee1584575ffunaffected
LinuxLinux5.18, 0, 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.