CVE-2026-93175 Linux kernel CVE debrief

Who should care

Defenders responsible for Linux kernel-based systems, particularly those using the affected drm/amd/display component, should assess exposure and prioritize patching. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review system configurations, update Linux kernel versions as necessary, and monitor system logs for potential exploitation attempts.

Why it matters

A vulnerability in the Linux kernel's drm/amd/display component can lead to a dangling pointer in the CRTC reset function, potentially causing system instability or exploitation. Defenders should prioritize verifying and applying patches, particularly for systems using affected Linux kernel versions.

• Potential system crashes or instability due to dangling pointer
• Increased risk of exploitation leading to denial of service or arbitrary code execution
• Need for verification of Linux kernel versions and patch application
• Potential impact on system availability and reliability

Technical summary

The vulnerability occurs in the amdgpu_dm_crtc_reset_state() function, which frees the old state before allocating a new one. If the new allocation fails, the function returns without updating the state pointer, leaving a dangling pointer to already freed memory. The issue has been resolved by allocating the new state first. The affected component is used in various Linux kernel versions, and defenders should assess exposure and prioritize patching. The vulnerability can cause system instability or exploitation, potentially leading to denial of service or arbitrary code execution.

Defensive priority

Defenders should prioritize verifying and applying patches for this vulnerability, particularly for systems using the affected Linux kernel versions.

Recommended defensive actions

• Verify and apply patches for this vulnerability
• Review system configurations and update Linux kernel versions as necessary
• Monitor system logs for potential exploitation attempts
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The vulnerability was found by Linux Verification Center (linuxtesting.org) with SVACE. The issue is resolved in the Linux kernel. The affected component is used in various Linux kernel versions. Defenders should verify and apply patches, review system configurations, and update Linux kernel versions as necessary. The vulnerability can cause system instability or exploitation, potentially leading to denial of service or arbitrary code execution.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.