Linux kernel amdgpu display core (DC/DM) (drm/amd/display): Missing or insufficient validation of user-supplied

Impact

Missing or insufficient validation of user-supplied parameters in the amdgpu display core (DC/DM). A value that crosses the ioctl boundary - a size, a count, an offset, a buffer-object mapping range - is trusted rather than checked, so a tenant can drive the driver outside the range its authors assumed. Where the unchecked value indexes or sizes a kernel allocation this is a memory-corruption primitive and therefore a host-compromise route out of a GPU container; where it only reaches a sanity check further down it costs the node a crash. Upstream fix: drm/amd/display: Add NULL check for clk_mgr and clk_mgr->funcs in dcn30_init_hw

Who can reach it

Local. Reachable by a local user with access to the DRM primary node, or an attacker who controls the attached display's EDID/DisplayPort topology. On headless Instinct nodes the display block is largely unused, which cuts real exposure sharply. Not reachable over the network and not reachable from a container that has no GPU device node mapped in.

What to do

Kernel-side fix: this lands in mainline Linux and flows into distro kernels (RHEL/Rocky, Ubuntu HWE, SLES) and into AMD's out-of-tree DKMS amdgpu package shipped with ROCm. Patch the kernel or the DKMS module, then **reload the amdgpu module or reboot the node** - you cannot fix a running driver in place. Reloading amdgpu requires no process holding /dev/kfd or a render node, so in practice this is a cordon + drain + reboot per node. Plan it as a rolling maintenance across the fleet; there is no VBIOS flash, no SBIOS/AGESA step and no firmware update involved. Nodes running the ROCm DKMS stack often lag mainline by a release or two, so confirm the fix is actually present in the AMD driver version you deploy rather than assuming a new distro kernel covers it.

References