CVE-2022-50867 (GCVE-0-2022-50867)

Vulnerability from cvelistv5 – Published: 2025-12-30 12:15 – Updated: 2026-08-05 08:59
VLAI
Title
drm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage adreno_show_object() is a trap! It will re-allocate the pointer it is passed on first call, when the data is ascii85 encoded, using kvmalloc/ kvfree(). Which means the data *passed* to it must be kvmalloc'd, ie. we cannot use the state_kcalloc() helper. This partially reverts commit ec8f1813bf8d ("drm/msm/a6xx: Replace kcalloc() with kvzalloc()"), but adds the missing kvfree() to fix the memory leak that was present previously. And adds a warning comment. Patchwork: https://patchwork.freedesktop.org/patch/507014/
Severity
7.8 (High)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Assigner
Linux CNA under the mitre root
CNA scorecard D 53/100 over 6639 records in the last 180 days details
References
Impacted products
Vendor Product Version CPE status
Linux Linux Affected: b859f9b009bbfbc236d9b076c64c59ccb41b8737 , < 4b1bbc0571a5d7ee10f754186dc3d619b9ced5c1 (git)
Affected: b859f9b009bbfbc236d9b076c64c59ccb41b8737 , < 83d18e9d9c0150d98dc24e3642ea93f5e245322c (git)
guessed Create a notification for this product.
Linux Linux Affected: 5.17
Unaffected: 0 , < 5.17 (semver)
Unaffected: 6.0.7 , ≤ 6.0.* (semver)
Unaffected: 6.1 , ≤ * (original_commit_for_fix)
guessed Create a notification for this product.
Show details on NVD website
To clipboard 

{
  "containers": {
    "cna": {
      "affected": [
        {
          "defaultStatus": "unaffected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c",
            "drivers/gpu/drm/msm/adreno/adreno_gpu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "lessThan": "4b1bbc0571a5d7ee10f754186dc3d619b9ced5c1",
              "status": "affected",
              "version": "b859f9b009bbfbc236d9b076c64c59ccb41b8737",
              "versionType": "git"
            },
            {
              "lessThan": "83d18e9d9c0150d98dc24e3642ea93f5e245322c",
              "status": "affected",
              "version": "b859f9b009bbfbc236d9b076c64c59ccb41b8737",
              "versionType": "git"
            }
          ]
        },
        {
          "defaultStatus": "affected",
          "product": "Linux",
          "programFiles": [
            "drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c",
            "drivers/gpu/drm/msm/adreno/adreno_gpu.c"
          ],
          "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
          "vendor": "Linux",
          "versions": [
            {
              "status": "affected",
              "version": "5.17"
            },
            {
              "lessThan": "5.17",
              "status": "unaffected",
              "version": "0",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "6.0.*",
              "status": "unaffected",
              "version": "6.0.7",
              "versionType": "semver"
            },
            {
              "lessThanOrEqual": "*",
              "status": "unaffected",
              "version": "6.1",
              "versionType": "original_commit_for_fix"
            }
          ]
        }
      ],
      "cpeApplicability": [
        {
          "nodes": [
            {
              "cpeMatch": [
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.0.7",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                },
                {
                  "criteria": "cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*",
                  "versionEndExcluding": "6.1",
                  "versionStartIncluding": "5.17",
                  "vulnerable": true
                }
              ],
              "negate": false,
              "operator": "OR"
            }
          ]
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage\n\nadreno_show_object() is a trap!  It will re-allocate the pointer it is\npassed on first call, when the data is ascii85 encoded, using kvmalloc/\nkvfree().  Which means the data *passed* to it must be kvmalloc\u0027d, ie.\nwe cannot use the state_kcalloc() helper.\n\nThis partially reverts commit ec8f1813bf8d (\"drm/msm/a6xx: Replace\nkcalloc() with kvzalloc()\"), but adds the missing kvfree() to fix the\nmemory leak that was present previously.  And adds a warning comment.\n\nPatchwork: https://patchwork.freedesktop.org/patch/507014/"
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "baseScore": 7.8,
            "baseSeverity": "HIGH",
            "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
            "version": "3.1"
          },
          "scenarios": [
            {
              "lang": "en",
              "value": "AV:L - The vulnerable show/encode path is reached after a local GPU hang or iova fault captures crash state via msm_gpu_crashstate_capture(); an unprivileged process triggers that through DRM render-node submits (MSM_GEM_SUBMIT). There is no network or adjacent-packet path into a6xx_show/adreno_show_object.\nAC:L - An attacker fully controls both sides: submit work that hangs or faults the a6xx GPU, then rely on the deterministic ascii85 reallocation in adreno_show_object() when the dump is read. No race or attacker-uncontrollable memory-layout precondition is required.\nPR:L - Unprivileged users can open /dev/dri/renderD* and hang the GPU. On the primary msm deployments (ChromeOS/Android), crash_reporter/udev_collector automatically reads /sys/class/devcoredump/devcdN/data for the adreno driver, invoking the bad kvfree without the attacker needing root. Choosing the higher-severity PR:L over PR:H for that reasonable scenario.\nUI:N - The attacker submits the hanging GPU work themselves, and automatic device-coredump collection invokes a6xx_show without any separate victim mount/open/interactive action.\nS:U - The invalid free corrupts host kernel allocator state within the same OS security authority; this is a local privilege-escalation class bug, not a VM escape, IOMMU bypass, or other cross-boundary impact.\nC:H - adreno_show_object() kvfree()s an interior pointer into a state_kcalloc() memobj (past list_head), corrupting kvmalloc/SLUB freelist metadata; that heap corruption can be leveraged for arbitrary kernel memory disclosure, matching kernel CVSS guidance for memory-corruption bugs.\nI:H - The same interior-pointer free (and subsequent double-free of the memobj on a6xx_gpu_state_destroy) corrupts heap freelists and adjacent objects, enabling reuse and write/control-flow hijacking primitives rather than a benign bounded fault.\nA:H - The gitlab issue closed by the fix reports that reading the devcoredump triggers memory corruption; invalid free/double-free produce kernel oops/panic, which is Availability High under kernel CVSS guidance."
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2026-08-05T08:59:53.122Z",
        "orgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "shortName": "Linux"
      },
      "references": [
        {
          "url": "https://git.kernel.org/stable/c/4b1bbc0571a5d7ee10f754186dc3d619b9ced5c1"
        },
        {
          "url": "https://git.kernel.org/stable/c/83d18e9d9c0150d98dc24e3642ea93f5e245322c"
        }
      ],
      "title": "drm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage",
      "x_generator": {
        "engine": "bippy-1.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
    "assignerShortName": "Linux",
    "cveId": "CVE-2022-50867",
    "datePublished": "2025-12-30T12:15:38.520Z",
    "dateReserved": "2025-12-30T12:06:07.136Z",
    "dateUpdated": "2026-08-05T08:59:53.122Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2022-50867",
      "date": "2026-11-10",
      "epss": "0.00145",
      "percentile": "0.03783"
    },
    "nvd": {
      "cve": {
        "affected": [
          {
            "affectedData": [
              {
                "defaultStatus": "unaffected",
                "product": "Linux",
                "programFiles": [
                  "drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c",
                  "drivers/gpu/drm/msm/adreno/adreno_gpu.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "lessThan": "4b1bbc0571a5d7ee10f754186dc3d619b9ced5c1",
                    "status": "affected",
                    "version": "b859f9b009bbfbc236d9b076c64c59ccb41b8737",
                    "versionType": "git"
                  },
                  {
                    "lessThan": "83d18e9d9c0150d98dc24e3642ea93f5e245322c",
                    "status": "affected",
                    "version": "b859f9b009bbfbc236d9b076c64c59ccb41b8737",
                    "versionType": "git"
                  }
                ]
              },
              {
                "defaultStatus": "affected",
                "product": "Linux",
                "programFiles": [
                  "drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c",
                  "drivers/gpu/drm/msm/adreno/adreno_gpu.c"
                ],
                "repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
                "vendor": "Linux",
                "versions": [
                  {
                    "status": "affected",
                    "version": "5.17"
                  },
                  {
                    "lessThan": "5.17",
                    "status": "unaffected",
                    "version": "0",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "6.0.*",
                    "status": "unaffected",
                    "version": "6.0.7",
                    "versionType": "semver"
                  },
                  {
                    "lessThanOrEqual": "*",
                    "status": "unaffected",
                    "version": "6.1",
                    "versionType": "original_commit_for_fix"
                  }
                ]
              }
            ],
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67"
          }
        ],
        "cveTags": [],
        "descriptions": [
          {
            "lang": "en",
            "value": "In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/a6xx: Fix kvzalloc vs state_kcalloc usage\n\nadreno_show_object() is a trap!  It will re-allocate the pointer it is\npassed on first call, when the data is ascii85 encoded, using kvmalloc/\nkvfree().  Which means the data *passed* to it must be kvmalloc\u0027d, ie.\nwe cannot use the state_kcalloc() helper.\n\nThis partially reverts commit ec8f1813bf8d (\"drm/msm/a6xx: Replace\nkcalloc() with kvzalloc()\"), but adds the missing kvfree() to fix the\nmemory leak that was present previously.  And adds a warning comment.\n\nPatchwork: https://patchwork.freedesktop.org/patch/507014/"
          }
        ],
        "id": "CVE-2022-50867",
        "lastModified": "2026-08-04T10:18:24.920",
        "metrics": {
          "cvssMetricV31": [
            {
              "cvssData": {
                "attackComplexity": "LOW",
                "attackVector": "LOCAL",
                "availabilityImpact": "HIGH",
                "baseScore": 7.8,
                "baseSeverity": "HIGH",
                "confidentialityImpact": "HIGH",
                "integrityImpact": "HIGH",
                "privilegesRequired": "LOW",
                "scope": "UNCHANGED",
                "userInteraction": "NONE",
                "vectorString": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
                "version": "3.1"
              },
              "exploitabilityScore": 1.8,
              "impactScore": 5.9,
              "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
              "type": "Secondary"
            }
          ]
        },
        "published": "2025-12-30T13:16:01.533",
        "references": [
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/4b1bbc0571a5d7ee10f754186dc3d619b9ced5c1"
          },
          {
            "source": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
            "url": "https://git.kernel.org/stable/c/83d18e9d9c0150d98dc24e3642ea93f5e245322c"
          }
        ],
        "sourceIdentifier": "416baaa9-dc9f-4396-8d5f-8c081fb06d67",
        "vulnStatus": "Deferred"
      }
    },
    "redhat_vex": {
      "aggregate_severity": "Important",
      "current_release_date": "2026-11-04T21:02:33+00:00",
      "cve": "CVE-2022-50867",
      "id": "CVE-2022-50867",
      "initial_release_date": "2022-01-01T00:00:00+00:00",
      "product_status:known_not_affected": "200",
      "source": "Red Hat CSAF VEX",
      "status": "final",
      "title": "kernel: Linux kernel: Memory leak in drm/msm/a6xx graphics driver",
      "url": "https://security.access.redhat.com/data/csaf/v2/vex/2022/cve-2022-50867.json",
      "version": "3"
    },
    "suse_vex": {
      "aggregate_severity": "moderate",
      "current_release_date": "2026-11-01T03:00:05Z",
      "cve": "CVE-2022-50867",
      "id": "CVE-2022-50867",
      "initial_release_date": "2025-12-31T00:30:55Z",
      "product_status:known_affected": "374",
      "product_status:known_not_affected": "490",
      "product_status:recommended": "87",
      "source": "SUSE CSAF VEX",
      "status": "interim",
      "title": "SUSE CVE CVE-2022-50867",
      "url": "https://ftp.suse.com/pub/projects/security/csaf-vex/2025/cve-2022-50867.json",
      "version": "26"
    }
  }
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.




Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline

Sightings and recorded dates, grouped by day · UTC

JSON
How durations are calculated

Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.

Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.

Loading timeline…




    Related by attack behaviour

    Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.