> CVE-2026-89828

« BACK_TO_HOME
PUBLISHED
2026-09-16 11:16
MODIFIED
2026-09-16 11:16
EPSS (Prob. Exploit)
0.22%
Top 88.2%
DATA SOURCES:
NVD 🔗 2026-09-16 FIRST EPSS 🔗 2026-10-25 OSV 🔗 2026-09-23 MSRC 🔗 2026-10-22

> DESCRIPTION

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.

> AFFECTED_PRODUCTS

ℹ️ Aucun produit affecté n'a encore été publié par NVD pour cette CVE.

> OSV (GOOGLE OPEN SOURCE VULNERABILITIES)

drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init()

AFFECTED PACKAGES:
Unknown / Unknown
Linux / Kernel

> HISTORIQUE DES MODIFICATIONS

Première apparition
16/09/2026 11:16
Source: NVD
Total des modifications: 0 Dernière mise à jour: 1 month ago

> REFERENCES

https://git.kernel.org/stable/c/3e234c6face8651045f46895dfe9c086ea64f03b
https://git.kernel.org/stable/c/e184e46ca1ba652ab8053a10a51b39aad06d3f5c
https://git.kernel.org/stable/c/e773798e14ac0aea54ca9676083b91f445e5bc59
« BACK_TO_HOME