{"dataType":"CVE_RECORD","dataVersion":"5.2","cveMetadata":{"cveId":"CVE-2022-50867","assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","state":"PUBLISHED","assignerShortName":"Linux","dateReserved":"2025-12-30T12:06:07.136Z","datePublished":"2025-12-30T12:15:38.520Z","dateUpdated":"2026-05-11T19:26:39.639Z"},"containers":{"cna":{"providerMetadata":{"orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux","dateUpdated":"2026-05-11T19:26:39.639Z"},"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'd, 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/"}],"affected":[{"product":"Linux","vendor":"Linux","defaultStatus":"unaffected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c","drivers/gpu/drm/msm/adreno/adreno_gpu.c"],"versions":[{"version":"b859f9b009bbfbc236d9b076c64c59ccb41b8737","lessThan":"4b1bbc0571a5d7ee10f754186dc3d619b9ced5c1","status":"affected","versionType":"git"},{"version":"b859f9b009bbfbc236d9b076c64c59ccb41b8737","lessThan":"83d18e9d9c0150d98dc24e3642ea93f5e245322c","status":"affected","versionType":"git"}]},{"product":"Linux","vendor":"Linux","defaultStatus":"affected","repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","programFiles":["drivers/gpu/drm/msm/adreno/a6xx_gpu_state.c","drivers/gpu/drm/msm/adreno/adreno_gpu.c"],"versions":[{"version":"5.17","status":"affected"},{"version":"0","lessThan":"5.17","status":"unaffected","versionType":"semver"},{"version":"6.0.7","lessThanOrEqual":"6.0.*","status":"unaffected","versionType":"semver"},{"version":"6.1","lessThanOrEqual":"*","status":"unaffected","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"operator":"OR","negate":false,"cpeMatch":[{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.0.7"},{"vulnerable":true,"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionStartIncluding":"5.17","versionEndExcluding":"6.1"}]}]}],"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"}}}}