drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init()

Summary

In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init() drmm_cgroup_register_region() is called before INIT_LIST_HEAD() and gpu_buddy_init() in amdgpu_vram_mgr_init(). If it fails, the function returns early and bypasses those initializations. Since adev->mman.initialized is set to true before amdgpu_vram_mgr_init() is called, a failure triggers amdgpu_ttm_fini(), which calls amdgpu_vram_mgr_fini(), which then: • Calls list_for_each_entry_safe() on reservations_pending and reserved_pages, whose list_head::next pointers are zero-initialized (NULL). The loop does not recognize them as empty and dereferences NULL. • Calls gpu_buddy_fini(), which iterates free_trees[] unconditionally via for_each_free_tree(). Since mm->free_trees is NULL (never allocated), this dereferences NULL. Both result in a kernel panic on the module load error path. Fix by moving drmm_cgroup_register_region() to after the list and buddy allocator are fully initialized, so the teardown path is safe to run.

Timeline

1. Sep 16, 2026, 10:31 AM UTCCVE published
2. Oct 19, 2026, 8:53 AM UTCRecord last updated

Affected versions

• Linux Linux

  From 2b624a2c18656ea32e0849e7bc0018ba3c97ca64 · fixed in e184e46ca1ba652ab8053a10a51b39aad06d3f5c; From 2b624a2c18656ea32e0849e7bc0018ba3c97ca64 · fixed in 3e234c6face8651045f46895dfe9c086ea64f03b; From 2b624a2c18656ea32e0849e7bc0018ba3c97ca64 · fixed in e773798e14ac0aea54ca9676083b91f445e5bc59

• Linux Linux

  6.14

• KernelLinux

  From 6.14.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5

References 3