CVE-2026-68259

Received Received - Intake

Out-of-Bounds Event ID Allocation in AMDKFD Linux Kernel

Publication date: 2026-08-10

Last updated on: 2026-08-19

Assigner: kernel.org

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)

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-08-10

Last Modified

2026-08-19

Generated

2026-08-31

AI Q&A

2026-08-10

EPSS Evaluated

2026-08-29

NVD

CVE-2026-68259

EUVD

EUVD-2026-55360

Affected Vendors & Products

Vendor	Product	Version / Range
linux	linux_kernel	*

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-UNKNOWN

Attack-Flow Graph

Executive Summary

This is a Linux kernel vulnerability in the AMDKFD driver where the function allocate_event_notification_slot does not validate the event ID bounds when allocating slots. The valid event IDs range from 0 to KFD_SIGNAL_EVENT_LIMIT, but the function allowed specifying an out-of-bounds event ID, which could lead to memory corruption or other issues.

Detection Guidance

This vulnerability is specific to the Linux kernel's drm/amdkfd component and relates to improper bounds checking in event id allocation. Detection requires checking kernel versions and examining the drm/amdkfd code for the allocate_event_notification_slot function. No network-specific detection commands are applicable.

Impact Analysis

This vulnerability could allow an attacker with local access to cause a denial of service, escalate privileges, or execute arbitrary code in the kernel. It primarily affects systems using AMD GPUs with the affected kernel driver.

Compliance Impact

This vulnerability does not directly affect compliance with standards like GDPR or HIPAA as it pertains to a memory management issue in the Linux kernel's AMDKFD driver. Compliance implications would depend on how the affected system is used, but the vulnerability itself is not a direct violation of these regulations.

Mitigation Strategies

Apply the kernel patch that adds bounds checking to allocate_event_notification_slot. Update to a kernel version containing the fix (commit 6853f1f6cbbeb3f53ebbbd7286536aeb2c5d5f50). If patching is not immediately possible, restrict access to CRIU functionality that uses this feature.

Hi! I’m here to help you understand CVE-2026-68259. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70