CVE-2026-68259

drm/amdkfd: Check bounds in allocate_event_notification_slot

N/A
Published: August 10, 2026 at 12:01 PM UTC
Updated: August 19, 2026 at 05:20 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.18 ≤ v < 6.1.1835.18 ≤ v < 6.12.1015.18 ≤ v < 6.18.425.18 ≤ v < 6.6.1485.18 ≤ v < 7.1.65.18 ≤ v < 7.240e8a766a761f7fdc8530347527b344fddf6f1a85.18
Vendor states this is fixed in 4622214f0542f64b02c250db0f9c677eeb032d9b (fixed)
Vendor states this is fixed in 50319efb865f72db45f191c8709511746d58ee0a (fixed)
Vendor states this is fixed in 6884fc142b17f456caac50c14505f509bfbcd012 (fixed)
Vendor states this is fixed in 85eedff5f0c4aba5a66bc37a1bd6bcecd0d77b53 (fixed)
Vendor states this is fixed in abeeb1947d81610c65349db4d89c6151f270e136 (fixed)
Vendor states this is fixed in bb52249fbbe948875155ccd45cd8d74bf4ae747b (fixed)
Vendor states this is fixed in 5.18 (unaffected)
Vendor states this is fixed in 6.1.183 (unaffected)
Vendor states this is fixed in 6.12.101 (unaffected)
Vendor states this is fixed in 6.18.42 (unaffected)
Vendor states this is fixed in 6.6.148 (unaffected)
Vendor states this is fixed in 7.1.6 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card