# CVE-2026-99149: drm/amdgpu: fix GEM object leak on ENOMEM in userptr ioctl


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-99149, GHSA-7fj6-92pf-cvxq, UBUNTU-CVE-2026-99149

## What is CVE-2026-99149?

CVE-2026-99149 is a vulnerability in Linux, published on 28 Oct 2026. 

### Official description

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

drm/amdgpu: fix GEM object leak on ENOMEM in userptr ioctl

When amdgpu_hmm_range_alloc() fails amdgpu_gem_userptr_ioctl() returns
-ENOMEM right away and skips the cleanup every other error path goes
through. The GEM object, the bo->parent reference on the VM root and the
MMU notifier registration are all left behind.

Use release_object here, not user_pages_done, range is still NULL at
this point.

(cherry picked from commit bbe739e407a542073ec1a7872b14843566b4919e)

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


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

Upgrade to a fixed version.

## Is CVE-2026-99149 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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