drm/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id
- 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.1.189, 6.6.158, 6.12.111, 6.18.53
- 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/amdkfd: Check bounds for allocate_sdma_queue restore_sdma_id allocate_sdma_queue has an option where the sdma queue id can be specified (used by CRIU). We weren't bounds-checking that value. Confirm it's less than the maximum number of queues.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 2485c12c980a36bb9e23ababb07d73c4ac6a45af · fixed in 41460d2dd0246f0ab7e80b103d34c8649e022999; From 2485c12c980a36bb9e23ababb07d73c4ac6a45af · fixed in 25e1b29ecc8da3609ba0072ca54a3b1fdd1578f3; From 2485c12c980a36bb9e23ababb07d73c4ac6a45af · fixed in 42f2bd50236b61ad0aeb2c233c990ee0d615fdad; From 2485c12c980a36bb9e23ababb07d73c4ac6a45af · fixed in dd2870ca036e1d51baa59f942007b36a595b5890; From 2485c12c980a36bb9e23ababb07d73c4ac6a45af · fixed in bfe9a7545b2a7be1c543f1741e16f2d5ec4116ae
- Linux Linux
5.18
- KernelLinux
From 5.18.0 · fixed in 6.1.189; From 6.2.0 · fixed in 6.6.158; From 6.7.0 · fixed in 6.12.111; From 6.13.0 · fixed in 6.18.53