{"api_version":"1","generated_at":"2026-06-02T09:42:03+00:00","cve":"CVE-2026-46211","urls":{"html":"https://cve.report/CVE-2026-46211","api":"https://cve.report/api/cve/CVE-2026-46211.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-46211","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-46211"},"summary":{"title":"drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata()","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata()\n\nmsm_ioctl_gem_info_get_metadata() always returns 0 regardless of\nerrors. When copy_to_user() fails or the user buffer is too small,\nthe error code stored in ret is ignored because the function\nunconditionally returns 0. This causes userspace to believe the\nioctl succeeded when it did not.\n\nAdditionally, kmemdup() can return NULL on allocation failure, but\nthe return value is not checked. This leads to a NULL pointer\ndereference in the subsequent copy_to_user() call.\n\nAdd the missing NULL check for kmemdup() and return ret instead of 0.\n\nNote that the SET counterpart (msm_ioctl_gem_info_set_metadata)\ncorrectly returns ret.\n\nPatchwork: https://patchwork.freedesktop.org/patch/714478/","state":"PUBLISHED","assigner":"Linux","published_at":"2026-05-28 10:16:36","updated_at":"2026-05-28 13:44:01"},"problem_types":[],"metrics":[],"references":[{"url":"https://git.kernel.org/stable/c/47cbfe2608314b833ad61a65827d8fb363bc2d2d","name":"https://git.kernel.org/stable/c/47cbfe2608314b833ad61a65827d8fb363bc2d2d","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/b079e85c91f446f29e808d8291189e897f1884ff","name":"https://git.kernel.org/stable/c/b079e85c91f446f29e808d8291189e897f1884ff","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/c57c861956b89f2e2528e6384d51e2dedd915809","name":"https://git.kernel.org/stable/c/c57c861956b89f2e2528e6384d51e2dedd915809","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/697e1a9559f6962f999cc4c748c2ffffcc0a7a7a","name":"https://git.kernel.org/stable/c/697e1a9559f6962f999cc4c748c2ffffcc0a7a7a","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-46211","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-46211","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9902cb999e4e913d98e8afe4b36c08e4a793e1ce 697e1a9559f6962f999cc4c748c2ffffcc0a7a7a git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9902cb999e4e913d98e8afe4b36c08e4a793e1ce c57c861956b89f2e2528e6384d51e2dedd915809 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9902cb999e4e913d98e8afe4b36c08e4a793e1ce b079e85c91f446f29e808d8291189e897f1884ff git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 9902cb999e4e913d98e8afe4b36c08e4a793e1ce 47cbfe2608314b833ad61a65827d8fb363bc2d2d git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 6.8","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.8 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.12.90 6.12.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 6.18.32 6.18.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.0.9 7.0.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.1-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"46211","cve":"CVE-2026-46211","epss":"0.000180000","percentile":"0.048460000","score_date":"2026-06-01","updated_at":"2026-06-02 00:05:20"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/msm/msm_drv.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"697e1a9559f6962f999cc4c748c2ffffcc0a7a7a","status":"affected","version":"9902cb999e4e913d98e8afe4b36c08e4a793e1ce","versionType":"git"},{"lessThan":"c57c861956b89f2e2528e6384d51e2dedd915809","status":"affected","version":"9902cb999e4e913d98e8afe4b36c08e4a793e1ce","versionType":"git"},{"lessThan":"b079e85c91f446f29e808d8291189e897f1884ff","status":"affected","version":"9902cb999e4e913d98e8afe4b36c08e4a793e1ce","versionType":"git"},{"lessThan":"47cbfe2608314b833ad61a65827d8fb363bc2d2d","status":"affected","version":"9902cb999e4e913d98e8afe4b36c08e4a793e1ce","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/msm/msm_drv.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"6.8"},{"lessThan":"6.8","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"6.12.*","status":"unaffected","version":"6.12.90","versionType":"semver"},{"lessThanOrEqual":"6.18.*","status":"unaffected","version":"6.18.32","versionType":"semver"},{"lessThanOrEqual":"7.0.*","status":"unaffected","version":"7.0.9","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.1-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.12.90","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"6.18.32","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.0.9","versionStartIncluding":"6.8","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.1-rc1","versionStartIncluding":"6.8","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata()\n\nmsm_ioctl_gem_info_get_metadata() always returns 0 regardless of\nerrors. When copy_to_user() fails or the user buffer is too small,\nthe error code stored in ret is ignored because the function\nunconditionally returns 0. This causes userspace to believe the\nioctl succeeded when it did not.\n\nAdditionally, kmemdup() can return NULL on allocation failure, but\nthe return value is not checked. This leads to a NULL pointer\ndereference in the subsequent copy_to_user() call.\n\nAdd the missing NULL check for kmemdup() and return ret instead of 0.\n\nNote that the SET counterpart (msm_ioctl_gem_info_set_metadata)\ncorrectly returns ret.\n\nPatchwork: https://patchwork.freedesktop.org/patch/714478/"}],"providerMetadata":{"dateUpdated":"2026-05-28T09:40:28.890Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/697e1a9559f6962f999cc4c748c2ffffcc0a7a7a"},{"url":"https://git.kernel.org/stable/c/c57c861956b89f2e2528e6384d51e2dedd915809"},{"url":"https://git.kernel.org/stable/c/b079e85c91f446f29e808d8291189e897f1884ff"},{"url":"https://git.kernel.org/stable/c/47cbfe2608314b833ad61a65827d8fb363bc2d2d"}],"title":"drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata()","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-46211","datePublished":"2026-05-28T09:40:28.890Z","dateReserved":"2026-05-13T15:03:33.105Z","dateUpdated":"2026-05-28T09:40:28.890Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-05-28 10:16:36","lastModifiedDate":"2026-05-28 13:44:01","problem_types":[],"metrics":[],"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"46211","Ordinal":"1","Title":"drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metada","CVE":"CVE-2026-46211","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"46211","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metadata()\n\nmsm_ioctl_gem_info_get_metadata() always returns 0 regardless of\nerrors. When copy_to_user() fails or the user buffer is too small,\nthe error code stored in ret is ignored because the function\nunconditionally returns 0. This causes userspace to believe the\nioctl succeeded when it did not.\n\nAdditionally, kmemdup() can return NULL on allocation failure, but\nthe return value is not checked. This leads to a NULL pointer\ndereference in the subsequent copy_to_user() call.\n\nAdd the missing NULL check for kmemdup() and return ret instead of 0.\n\nNote that the SET counterpart (msm_ioctl_gem_info_set_metadata)\ncorrectly returns ret.\n\nPatchwork: https://patchwork.freedesktop.org/patch/714478/","Type":"Description","Title":"drm/msm/gem: fix error handling in msm_ioctl_gem_info_get_metada"}]}}}