CVE-2026-89808
- Source
- https://cve.org/CVERecord?id=CVE-2026-89808
- Import Source
- https://storage.googleapis.com/osv-test-cve-osv-conversion/osv-output/CVE-2026-89808.json
- JSON Data
- https://api.test.osv.dev/v1/vulns/CVE-2026-89808
- Downstream
- Related
- Published
- 2026-09-16T10:30:41Z
- Modified
- 2026-09-25T18:27:32Z
- Severity
-
- 7.8 (High) CVSS_V3 - CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CVSS Calculator
- Summary
- drm/amdkfd: Fix the case that vm range is hole at svm_migrate_copy_to_vram
- Details
-
In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Fix the case that vm range is hole at svm_migrate_copy_to_vram
When migration vm range is hole at cpu side(MIGRATE_PFN_MIGRATE set + MIGRATE_PFN_VALID unset) driver still allocates device pages. There is no dma map of src pages and migration. j is 0 and svm_migrate_copy_memory_gart() will return an uninitialized r. That can trigger out_free_vram_pages to drop all VRAM just set up.
Initialize r and only call the last svm_migrate_copy_memory_gart if j > 0.
Current code postponed the last page to the final copy. This patch flushes on the last page when reach to the end of current drm_buddy_block; avoids another svm_migrate_copy_memory_gart.
- Database specific
{ "cna_assigner": "Linux", "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89808.json" }- References
-
- https://git.kernel.org/stable/c/0a9a0e8a97da70a0336c9115178aaf1be29bcfb1
- https://git.kernel.org/stable/c/520e345ffe05aabef1db82beda4288afb1757ff2
- https://git.kernel.org/stable/c/ae806a95b28fcecb913430cfa45a252e91a945d6
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/89xxx/CVE-2026-89808.json
- https://nvd.nist.gov/vuln/detail/CVE-2026-89808
- https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git