{"api_version":"1","generated_at":"2026-09-28T15:30:20+00:00","cve":"CVE-2026-93175","urls":{"html":"https://cve.report/CVE-2026-93175","api":"https://cve.report/api/cve/CVE-2026-93175.json","docs":"https://cve.report/api","cve_org":"https://www.cve.org/CVERecord?id=CVE-2026-93175","nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-93175"},"summary":{"title":"drm/amd/display: Fix dangling pointer in CRTC reset function","description":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Fix dangling pointer in CRTC reset function\n\namdgpu_dm_crtc_reset_state() frees the old state before allocating\na new one. If kzalloc() fails, the function returns without updating\nthe state pointer, leaving a dangling pointer to already freed memory.\n\nFix this by allocating the new state first. On allocation failure, the\nold state remains untouched and the function safely returns.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\n[adjust for movement around current amd-staging-drm-next]","state":"PUBLISHED","assigner":"Linux","published_at":"2026-09-17 17:18:13","updated_at":"2026-09-18 18:18:23"},"problem_types":[],"metrics":[{"version":"3.1","source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"}},{"version":"3.1","source":"CNA","type":"DECLARED","score":"7.8","severity":"HIGH","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","data":{"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"}}],"references":[{"url":"https://git.kernel.org/stable/c/0aeed866cb938943908c3ba46422128e49d2d080","name":"https://git.kernel.org/stable/c/0aeed866cb938943908c3ba46422128e49d2d080","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://git.kernel.org/stable/c/32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5","name":"https://git.kernel.org/stable/c/32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5","refsource":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","tags":[],"title":"","mime":"","httpstatus":"","archivestatus":"0"},{"url":"https://www.cve.org/CVERecord?id=CVE-2026-93175","name":"CVE Program record","refsource":"CVE.ORG","tags":["canonical"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-93175","name":"NVD vulnerability detail","refsource":"NVD","tags":["canonical","analysis"]}],"affected":[{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e7b07ceef2a650e5ed8ca37997689e086c680daf 32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected e7b07ceef2a650e5ed8ca37997689e086c680daf 0aeed866cb938943908c3ba46422128e49d2d080 git","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"affected 4.15","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 4.15 semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.2.6 7.2.* semver","platforms":[]},{"source":"CNA","vendor":"Linux","product":"Linux","version":"unaffected 7.3-rc1 * original_commit_for_fix","platforms":[]}],"timeline":[],"solutions":[],"workarounds":[],"exploits":[],"credits":[],"nvd_cpes":[],"vendor_comments":[],"enrichments":{"kev":null,"epss":{"cve_year":"2026","cve_id":"93175","cve":"CVE-2026-93175","epss":"0.001540000","percentile":"0.048960000","score_date":"2026-09-21","updated_at":"2026-09-22 00:03:18"},"legacy_qids":[]},"source_records":{"cve_program":{"containers":{"cna":{"affected":[{"defaultStatus":"unaffected","product":"Linux","programFiles":["drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crtc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"lessThan":"32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5","status":"affected","version":"e7b07ceef2a650e5ed8ca37997689e086c680daf","versionType":"git"},{"lessThan":"0aeed866cb938943908c3ba46422128e49d2d080","status":"affected","version":"e7b07ceef2a650e5ed8ca37997689e086c680daf","versionType":"git"}]},{"defaultStatus":"affected","product":"Linux","programFiles":["drivers/gpu/drm/amd/display/amdgpu_dm/amdgpu_dm_crtc.c"],"repo":"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git","vendor":"Linux","versions":[{"status":"affected","version":"4.15"},{"lessThan":"4.15","status":"unaffected","version":"0","versionType":"semver"},{"lessThanOrEqual":"7.2.*","status":"unaffected","version":"7.2.6","versionType":"semver"},{"lessThanOrEqual":"*","status":"unaffected","version":"7.3-rc1","versionType":"original_commit_for_fix"}]}],"cpeApplicability":[{"nodes":[{"cpeMatch":[{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.2.6","versionStartIncluding":"4.15","vulnerable":true},{"criteria":"cpe:2.3:o:linux:linux_kernel:*:*:*:*:*:*:*:*","versionEndExcluding":"7.3-rc1","versionStartIncluding":"4.15","vulnerable":true}],"negate":false,"operator":"OR"}]}],"descriptions":[{"lang":"en","value":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Fix dangling pointer in CRTC reset function\n\namdgpu_dm_crtc_reset_state() frees the old state before allocating\na new one. If kzalloc() fails, the function returns without updating\nthe state pointer, leaving a dangling pointer to already freed memory.\n\nFix this by allocating the new state first. On allocation failure, the\nold state remains untouched and the function safely returns.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\n[adjust for movement around current amd-staging-drm-next]"}],"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 dangling crtc->state is created in amdgpu_dm_crtc_reset_state(), which drm_mode_config_reset() invokes from drm_atomic_helper_resume() in dm_destroy_cached_state(). That runs from dm_resume() on S3 (amdgpu_pmops_resume -> amdgpu_device_resume) and on runtime resume when drm_open/amdgpu_driver_open_kms or amdgpu_drm_ioctl call pm_runtime_get_sync(). No protocol message carries the trigger.\nAC:L - After a successful amdgpu_dm_crtc_init() reset, crtc->state is live. The buggy amdgpu_dm_crtc_reset_state() then always kfree's it via amdgpu_dm_crtc_destroy_state() before kzalloc_obj(*state); on GFP_KERNEL ENOMEM it returns without clearing crtc->state. A local attacker can force that allocation failure with memory pressure; there is no race.\nPR:L - amdgpu_driver_open_kms() has no capable() check and always calls pm_runtime_get_sync(); amdgpu_drm_ioctl() does the same before drm_ioctl(). Access is the usual /dev/dri/cardN and renderD* nodes granted to the seat user by logind ACLs or the video/render group, not init-namespace root.\nUI:N - The attacker opens /dev/dri/renderD* or issues an amdgpu ioctl after amdgpu autosuspend (pm_runtime_put_autosuspend, 5s delay on the default BACO/PX/BOCO path when no CRTC is active); dm_resume() then runs drm_mode_config_reset() without another user mounting media or plugging hardware.\nS:U - The use-after-free is of host-kernel dm_crtc_state on the amdgpu display CRTC. It does not escape a KVM/Xen guest, bypass the IOMMU, or leave a sandbox.\nC:H - amdgpu_dm_crtc_destroy_state() kfree's the live dm_crtc_state while crtc->state still points at it. drm_atomic_helper_commit_duplicated_state() then loads that freed object as old_state, including dc_stream_state *stream and drm_crtc_state mode_blob/commit/event pointers, a slab UAF read.\nI:H - The same dangling crtc->state is installed as old_state and later passed to atomic_destroy_state again (double-free). Heap reuse of dm_crtc_state lets an attacker control stream, commit, and event pointers consumed by the resume atomic commit, a write and control-flow primitive.\nA:H - drm_atomic_helper_commit_duplicated_state() immediately dereferences the freed dm_crtc_state after drm_mode_config_reset(), causing a kernel oops; the later second destroy is a double-free. Either path oopses or panics the host."}]}],"providerMetadata":{"dateUpdated":"2026-09-18T17:56:20.794Z","orgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","shortName":"Linux"},"references":[{"url":"https://git.kernel.org/stable/c/32bd68edbc6cbcfac0e4033b64f0bcadbf0efef5"},{"url":"https://git.kernel.org/stable/c/0aeed866cb938943908c3ba46422128e49d2d080"}],"title":"drm/amd/display: Fix dangling pointer in CRTC reset function","x_generator":{"engine":"bippy-1.2.0"}}},"cveMetadata":{"assignerOrgId":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","assignerShortName":"Linux","cveId":"CVE-2026-93175","datePublished":"2026-09-17T16:12:04.609Z","dateReserved":"2026-09-17T16:02:15.090Z","dateUpdated":"2026-09-18T17:56:20.794Z","state":"PUBLISHED"},"dataType":"CVE_RECORD","dataVersion":"5.2"},"nvd":{"publishedDate":"2026-09-17 17:18:13","lastModifiedDate":"2026-09-18 18:18:23","problem_types":[],"metrics":{"cvssMetricV31":[{"source":"416baaa9-dc9f-4396-8d5f-8c081fb06d67","type":"Secondary","cvssData":{"version":"3.1","vectorString":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","baseScore":7.8,"baseSeverity":"HIGH","attackVector":"LOCAL","attackComplexity":"LOW","privilegesRequired":"LOW","userInteraction":"NONE","scope":"UNCHANGED","confidentialityImpact":"HIGH","integrityImpact":"HIGH","availabilityImpact":"HIGH"},"exploitabilityScore":1.8,"impactScore":5.9}]},"configurations":[]},"legacy_mitre":{"record":{"CveYear":"2026","CveId":"93175","Ordinal":"1","Title":"drm/amd/display: Fix dangling pointer in CRTC reset function","CVE":"CVE-2026-93175","Year":"2026"},"notes":[{"CveYear":"2026","CveId":"93175","Ordinal":"1","NoteData":"In the Linux kernel, the following vulnerability has been resolved:\n\ndrm/amd/display: Fix dangling pointer in CRTC reset function\n\namdgpu_dm_crtc_reset_state() frees the old state before allocating\na new one. If kzalloc() fails, the function returns without updating\nthe state pointer, leaving a dangling pointer to already freed memory.\n\nFix this by allocating the new state first. On allocation failure, the\nold state remains untouched and the function safely returns.\n\nFound by Linux Verification Center (linuxtesting.org) with SVACE.\n\n[adjust for movement around current amd-staging-drm-next]","Type":"Description","Title":"drm/amd/display: Fix dangling pointer in CRTC reset function"}]}}}