In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Check bounds in allocate_event_notification_slot
The valid event ids go from 0 to KFD_SIGNAL_EVENT_LIMIT
allocate_event_notification_slot has an option to specify an event id to allocate at, used by CRIU. We werent checking the bounds on that value.
Check them.
v2: Lower bounds check is unecessary because of idr_alloc already rejecting negative numbers. Upper bounds check should be KFD_SIGNAL_EVENT_LIMIT since the signal mode mappings might not yet exist
(cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)
References
- https://git.kernel.org/stable/c/4622214f0542f64b02c250db0f9c677eeb032d9b
- https://git.kernel.org/stable/c/50319efb865f72db45f191c8709511746d58ee0a
- https://git.kernel.org/stable/c/85eedff5f0c4aba5a66bc37a1bd6bcecd0d77b53
- https://git.kernel.org/stable/c/abeeb1947d81610c65349db4d89c6151f270e136
- https://git.kernel.org/stable/c/bb52249fbbe948875155ccd45cd8d74bf4ae747b