drm/amdgpu: clamp the isolation index for rings outside a partition
- 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.15, 6.18.51, 7.2.5
- 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
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdgpu: clamp the isolation index for rings outside a partition adev->isolation[] has one slot per partition, but a ring that is not assigned to one keeps AMDGPU_XCP_NO_PARTITION, which is ~0, so indexing the array with it is out of bounds. SDMA submissions hit this on both the isolation enforcement and the VM flush path and trip UBSAN. Fall back to the first slot the way the cleaner shader path already does, and stop taking the address before the ring type check that makes it relevant.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From bd22e44ad415ac22e3a4f9a983d2a085f6cb4427 · fixed in 964de255497ffd7cb8a86e405b8ac6d927e7e177; From bd22e44ad415ac22e3a4f9a983d2a085f6cb4427 · fixed in 0bfb938182d1313e5cac32ae38dbaaa4eabe4af4; From bd22e44ad415ac22e3a4f9a983d2a085f6cb4427 · fixed in b30900566642ceb2c9e12b56c2afec28d0fd91a0; From 6.14.9 · fixed in 6.15
- Linux Linux
6.15
- KernelLinux
From 6.15.0 · fixed in 6.18.51; From 6.19.0 · fixed in 7.2.5