Skip to content
Heist/ feed
Back to feed
HighFix available

drm/fb-helper: Fix out-of-bounds access

Type: advisorySources: OSV

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.

Products
Kernel
Affected versions
Not specified
Fixed versions
5.19.2
CVEs
CVE-2022-50221
Confirmed fixed CVEs
Not specified
Updated in this feed
8 Nov 2026, 00:47 UTC · Revision 1

Source evidence

drm/fb-helper: Fix out-of-bounds access

core-osv · Original source

Published 18 Jun 2025, 11:03 UTC

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.

osv:CVE-2022-50221

Kernel

Fixed versions: 5.19.2

Complete source record
{
  "id": "e18c4a841d3a3f6abf451da6ea33b9e3b5fe738e275704838a22d49a4fc25f76",
  "url": "https://osv.dev/vulnerability/CVE-2022-50221",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "title": "drm/fb-helper: Fix out-of-bounds access",
    "summary": "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.",
    "evidence": "osv:CVE-2022-50221",
    "products": [
      {
        "name": {
          "value": "Kernel",
          "evidence": "/affected/1/package/name"
        },
        "prerequisites": [],
        "fixed_versions": [
          {
            "value": "5.19.2",
            "evidence": "/affected/1/ranges"
          }
        ],
        "affected_versions": []
      }
    ],
    "severity": "high",
    "structured": {
      "id": "CVE-2022-50221",
      "aliases": [
        "CVE-2022-50221"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
              "type": "GIT",
              "events": [
                {
                  "introduced": "67b723f5b74254d27962b1b59bddfee1584575ff"
                },
                {
                  "fixed": "9c49ac792c639dbec0728b513329a32461f72253"
                },
                {
                  "fixed": "ae25885bdf59fde40726863c57fd20e4a0642183"
                }
              ]
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50221.json"
          }
        },
        {
          "ranges": [
            {
              "type": "ECOSYSTEM",
              "events": [
                {
                  "introduced": "5.18.0"
                },
                {
                  "fixed": "5.19.2"
                }
              ]
            }
          ],
          "package": {
            "name": "Kernel",
            "ecosystem": "Linux"
          },
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2022-50221.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:52.478447329Z",
      "provider": "osv",
      "references": [
        "https://git.kernel.org/stable/c/9c49ac792c639dbec0728b513329a32461f72253",
        "https://git.kernel.org/stable/c/ae25885bdf59fde40726863c57fd20e4a0642183",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50221.json",
        "https://nvd.nist.gov/vuln/detail/CVE-2022-50221",
        "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
      ],
      "provider_metadata": {
        "cna_assigner": "Linux",
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2022/50xxx/CVE-2022-50221.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2022-50221",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 521083,
  "published_at": "2025-06-18T11:03:56.096+00:00"
}