AMD amdgpu driver CVE-2026-43603

Exploitation requires local access to the affected system and the ability to reach the vulnerable AMD GPU (amdgpu) Linux kernel driver code path - typically interaction with the DRM/GPU device interface. The CVSS vector (AV:L) confirms this is local, not remote, which is the primary limiting factor. The exact feature, ioctl, or configuration that triggers the NULL pointer dereference is not described in the available sources, so it cannot be stated which operation or deployment mode is required. Impact is limited to availability (kernel crash / denial of service); there is no confidentiality or integrity impact per the vector.

This is a moderate-severity, availability-only issue, not a high-priority emergency. The CVSS 4.0 vector (AV:L/AC:L/AT:N/PR:N/UI:N) scores 6.9 and indicates a local attack vector with low complexity and no privileges or user interaction, impacting only availability (VA:H) with no confidentiality or integrity effect (VC:N/VI:N) - consistent with a CWE-476 NULL pointer dereference that crashes the kernel (denial of service). The vuln.today decision label is 'this_month,' signaling it should be remediated in a routine patch cycle rather than immediately. There is no CISA KEV listing, no EPSS score supplied, and no public exploit identified at time of analysis, so there is no evidence of active or widespread exploitation. The PR:N rating means no authentication is required at the CVSS level, but the local (AV:L) vector inherently requires the attacker to already have a local foothold and the ability to reach the GPU driver code path, which substantially limits real-world risk versus a remote flaw. One signal to verify: PR:N implies any local user can trigger it, but reaching the AMD GPU driver in practice generally requires access to the DRM/render device interface - confirm whether your deployment grants unprivileged users that access.

A local attacker with the ability to interact with the AMD GPU driver interface triggers the vulnerable code path, causing a NULL pointer dereference that panics the kernel and crashes the host. The result is a denial of service (system reboot/hang) affecting all users of that machine. No public exploit is identified, and the specific trigger is not described in the available sources.