# CVE-2026-63882: drm/amdkfd: fix NULL pointer bug in svm_range_set_attr

> A local attacker can cause a denial of service in the Linux kernel by triggering a NULL pointer dereference in the AMD KFD driver.

- **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:** 19 Jul 2026
- **Updated:** 20 Jul 2026
- **Also known as:** AZL-92799, BELL-CVE-2026-63882, DEBIAN-CVE-2026-63882, GHSA-vf7c-595g-hm5x, ROOT-OS-UBUNTU-2204-CVE-2026-63882, UBUNTU-CVE-2026-63882

## What is CVE-2026-63882?

CVE-2026-63882 is a vulnerability in Linux, published on 19 Jul 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: fix NULL pointer bug in svm_range_set_attr

The process_info could be NULL if user doesn't call kfd_ioctl_acquire_vm
before calling kfd_ioctl_svm.

(cherry picked from commit 83a26c812e0529eb040d31a76f73e33e637243d4)

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


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

Apply the vendor's patch.

## Is CVE-2026-63882 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63882 is a vulnerability in Linux, published on 19 Jul 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-63882 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-63882/ (Markdown: https://insights.sbomify.com/CVE-2026-63882/index.md)
```

## Sources

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

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