# CVE-2026-68259: drm/amdkfd: Check bounds in allocate_event_notification_slot

> A missing bounds check in the Linux kernel's AMD KFD driver allows local attackers to trigger memory corruption or denial of service via crafted event IDs.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Aug 2026
- **Updated:** 19 Aug 2026
- **Also known as:** BELL-CVE-2026-68259, DEBIAN-CVE-2026-68259, GHSA-3gmf-h2jg-hwv2, UBUNTU-CVE-2026-68259

## What is CVE-2026-68259?

CVE-2026-68259 is a missing authorization vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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)

## Which versions are affected by CVE-2026-68259?


## How do I fix CVE-2026-68259?

Apply the vendor's patch.

## Is CVE-2026-68259 being exploited?

There is no known exploitation of CVE-2026-68259 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-68259 and fix it if it is affected.

What it is: CVE-2026-68259 is a missing authorization vulnerability in Linux, published on 10 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-68259 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-68259/ (Markdown: https://insights.sbomify.com/CVE-2026-68259/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-68259
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-68259
- OSV: https://osv.dev/vulnerability/CVE-2026-68259

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-68259/
Summaries are generated and may contain mistakes; the official description above is the record.