drm/amdkfd: Check bounds on CRIU restore queue type and mqd size
- 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.6.160, 6.12.114, 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: partial
Summary
In the Linux kernel, the following vulnerability has been resolved: drm/amdkfd: Check bounds on CRIU restore queue type and mqd size We weren't checking whether the values provided in the private data in kfd CRIU restore were within bounds. For queue type, add a KFD_QUEUE_TYPE_MAX and ensure the provided type is less than it. For mqd_size, add new function mqd_size_from_queue_type and confirm that the provided mqd_size matches expectations. (cherry picked from commit f19d8086f6644083c913d70bfdeee20e1b6f46a5)
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- Linux Linux
From 42c6c48214b726c30918e8dc80e2168607d13ae4 · fixed in 2b817c0dfc653bf33d0e0ab8155ff7807a617487; From 42c6c48214b726c30918e8dc80e2168607d13ae4 · fixed in 1956aa246c65c5895589664ccb37d0710aa8d304; From 42c6c48214b726c30918e8dc80e2168607d13ae4 · fixed in fd1691ec62701c982ea32e749678988c67fd4c21; From 42c6c48214b726c30918e8dc80e2168607d13ae4 · fixed in cc10a5839756982504ee8568fc1e1625962ab7f8; From 42c6c48214b726c30918e8dc80e2168607d13ae4 · fixed in 47ea05f246bebc81c7796f56265cffd812cf0601
- Linux Linux
5.18
- KernelLinux
From 5.18.0 · fixed in 6.6.160; From 6.7.0 · fixed in 6.12.114; From 6.13.0 · fixed in 6.18.42; From 6.19.0 · fixed in 7.1.6