drm/amdkfd: Check bounds on allocate_doorbell
- 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 on allocate_doorbell allocated_doorbell has an option to set the doorbell id to a specific value (used by CRIU). This value was not bounds checked. Check to confirm it's less than KFD_MAX_NUM_OF_QUEUES_PER_PROCESS.
Timeline
- CVE published
- Record last updated
Affected versions
- Linux Linux
From 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 · fixed in 7e06636260a2d95e3fa181bc337d0eeb812b7a41; From 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 · fixed in 3d2ddfc9b361b0d38c3ff4804ce42503e4bc97de; From 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 · fixed in e0cecd04a4fc4c75e375b91cf53eab5ba2e4ab7f; From 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 · fixed in c2c89118c27cbd3adace62c5df19d15b0e96ade1; From 5bb6a8fa75fcfda93592bee0a4910420ceab15f3 · fixed in 1f087bb8cf9e8797633da35c85435e557ef74d06
- 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