drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init()
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.
- Products
- Kernel
- Affected versions
- Not specified
- Fixed versions
- 6.18.51, 7.2.5
- CVEs
- CVE-2026-89828
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 11:15 UTC · Revision 1
Source evidence
drm/amdgpu: Fix init ordering in amdgpu_vram_mgr_init()
core-osv · Original sourcePublished 16 Sept 2026, 10:31 UTC
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.
osv:CVE-2026-89828
Kernel
Fixed versions: 6.18.51, 7.2.5
Complete source record
{
"id": "e1e64f038a185ce712b13f80bcc532351b0960319b0b9e2ba46018c78bc6b724",
"url": "https://osv.dev/vulnerability/CVE-2026-89828",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "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.",
"evidence": "osv:CVE-2026-89828",
"products": [
{
"name": {
"value": "Kernel",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "6.18.51",
"evidence": "/affected/1/ranges"
},
{
"value": "7.2.5",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "CVE-2026-89828",
"aliases": [
"CVE-2026-89828"
],
"affected": [
{
"ranges": [
{
"repo": "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git",
"type": "GIT",
"events": [
{
"introduced": "2b624a2c18656ea32e0849e7bc0018ba3c97ca64"
},
{
"fixed": "e184e46ca1ba652ab8053a10a51b39aad06d3f5c"
},
{
"fixed": "3e234c6face8651045f46895dfe9c086ea64f03b"
},
{
"fixed": "e773798e14ac0aea54ca9676083b91f445e5bc59"
}
]
}
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89828.json"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.14.0"
},
{
"fixed": "6.18.51"
}
]
},
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "6.19.0"
},
{
"fixed": "7.2.5"
}
]
}
],
"package": {
"name": "Kernel",
"ecosystem": "Linux"
},
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-89828.json"
}
}
],
"modified": "2026-10-28T02:30:28.042132755Z",
"provider": "osv",
"references": [
"https://git.kernel.org/stable/c/3e234c6face8651045f46895dfe9c086ea64f03b",
"https://git.kernel.org/stable/c/e184e46ca1ba652ab8053a10a51b39aad06d3f5c",
"https://git.kernel.org/stable/c/e773798e14ac0aea54ca9676083b91f445e5bc59",
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89828.json",
"https://nvd.nist.gov/vuln/detail/CVE-2026-89828",
"https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git"
],
"provider_metadata": {
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89828.json"
}
},
"related_cves": [
{
"value": "CVE-2026-89828",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 494882,
"published_at": "2026-09-16T10:31:00.827+00:00"
}