# CVE-2026-98910: drm/amdkfd: Unwind debug trap enable on copy_to_user failure


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 23 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** AZL-110674, BELL-CVE-2026-98910, DEBIAN-CVE-2026-98910, GHSA-9wgp-44pj-7g49, UBUNTU-CVE-2026-98910

## What is CVE-2026-98910?

CVE-2026-98910 is a vulnerability in Linux, published on 23 Oct 2026. 

### Official description

In the Linux kernel, the following vulnerability has been resolved:

drm/amdkfd: Unwind debug trap enable on copy_to_user failure

If kfd_dbg_trap_enable() fails while copying runtime_info to userspace,
it had already activated the trap, set debug_trap_enabled, taken an extra
process reference, and opened the debug event file. Return -EFAULT without
unwinding that state, leaving inconsistent trap state and a refcount
imbalance that could break later DISABLE/ENABLE.

On copy_to_user failure, deactivate the trap and undo the rest of the
enable setup before returning.

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


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

Upgrade to a fixed version.

## Is CVE-2026-98910 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98910 is a vulnerability in Linux, published on 23 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-98910 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-98910/ (Markdown: https://insights.sbomify.com/CVE-2026-98910/index.md)
```

## Sources

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

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