drm/amdkfd: fix 32-bit overflow in CWSR total size calculation
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.12.101, 6.18, 6.18.42, 7.1.6
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: fix 32-bit overflow in CWSR total size calculation total_cwsr_size was computed in 32-bit before being used as a BO/SVM allocation size. With large ctx_save_restore_area_size and debug_memory_size multiplied by the XCC count, the product can wrap, yielding an undersized CWSR save area that firmware later overruns. Promote total_cwsr_size to u64 and use check_add_overflow()/ check_mul_overflow() in both kfd_queue_acquire_buffers() and kfd_queue_release_buffers(). (cherry picked from commit 319f7e13423ae3f486b9aea82f9ad2d6af0ee608)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Linux Linux
From 325aa07165394b8e866ffe9ec1d4c99d9195b2f2 · fixed in b88ffe6593607364a8c06a48c6f29e55437cdf8e; From d15deafab5d722afb9e2f83c5edcdef9d9d98bd1 · fixed in abce3276c57e36c955627307469b9f009057a467; From d15deafab5d722afb9e2f83c5edcdef9d9d98bd1 · fixed in 865532d54eb57b660b1cb1b0e1755776ce21b849; From d15deafab5d722afb9e2f83c5edcdef9d9d98bd1 · fixed in 2b0386d4293920e690c0e017708f999b93cc729b; From 6.12.59 · fixed in 6.12.101; From 6.17.9 · fixed in 6.18
- Linux Linux
6.18
- KernelLinux
fixed in 6.12.101; From 6.13.0 · fixed in 6.18.42; From 6.18.0 · fixed in 7.1.6