Nixpkgs security tracker

Login with GitHub
⚠️ You are using a production deployment that is still only suitable for demo purposes. Any work done in this might be wiped later without notice.

Suggestion detail

Dismissed
(max. allowed matches exceeded)
created 3 weeks, 6 days ago Activity log
  • Created & dismissed (max. allowed matches exceeded) suggestion
drm/amdkfd: Check bounds in allocate_event_notification_slot

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 weren't 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)

Affected products

Linux
  • <abeeb1947d81610c65349db4d89c6151f270e136
  • <7.1.6
  • <6.12.101
  • <bb52249fbbe948875155ccd45cd8d74bf4ae747b
  • =<6.6.*
  • =<*
  • <6.6.148
  • <85eedff5f0c4aba5a66bc37a1bd6bcecd0d77b53
  • <4622214f0542f64b02c250db0f9c677eeb032d9b
  • =<6.18.*
  • <6.18.42
  • =<6.12.*
  • <50319efb865f72db45f191c8709511746d58ee0a
  • =<7.1.*