CVE-2026-68259: drm/amdkfd: Check bounds in allocate_event_notification_slot
In the Linux kernel, the following vulnerability has been resolved:
drm/amdkfd: Check bounds in allocateeventnotificationslot
The valid event ids go from 0 to KFDSIGNALEVENTLIMIT
allocateeventnotificationslot 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 idralloc already rejecting negative numbers. Upper bounds check should be KFDSIGNALEVENTLIMIT since the signal mode mappings might not yet exist
(cherry picked from commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50)
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-68259?
The severity of CVE-2026-68259 is rated at 34.
How do I fix CVE-2026-68259?
To fix CVE-2026-68259, update your Linux kernel to the latest version where this vulnerability has been resolved.
What systems are affected by CVE-2026-68259?
CVE-2026-68259 affects systems running vulnerable versions of the Linux kernel that include the drm/amdkfd module.
What does CVE-2026-68259 affect?
CVE-2026-68259 affects the event notification slot allocation in the drm/amdkfd component of the Linux kernel.
What is the nature of the issue in CVE-2026-68259?
CVE-2026-68259 involves a lack of bounds checking in the allocate_event_notification_slot function, which can lead to vulnerabilities.