CVE-2026-68259
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)
CSIRTS triage
- What
- Missing bounds checking in drm/amdkfd's allocate_event_notification_slot function allows out-of-bounds memory access.
- Who is affected
- Systems running affected Linux kernel versions with AMD KFD driver enabled.
- Urgency
- Medium severity (CVSS 5.5) memory corruption risk; update kernel to address the bounds check.
- Action
- Update to a patched Linux kernel version that includes the bounds checking fix for drm/amdkfd.
AI-assisted analysis generated from the source advisory — verify against the original.
⚡ Watch CVE-2026-68259
Get an email if CVE-2026-68259 is added to CISA KEV, gains public exploit code, or a new advisory cites it — max one per day, one-click unsubscribe.
Exploitation outlook
- Low exploitation risk0.17% 30-day exploitation probability — currently an unlikely target, but scores change as exploit code circulates. Riskier than 7% of all EPSS-scored CVEs.
Advisory coverage (2)
External references
Embed the live status
— this badge updates automatically when the KEV or exploit status changes. How to embed it →
[](https://www.csirts.com/cve/CVE-2026-68259)