# CVE-2026-98518: drm/nouveau/dmem: pin VRAM for the whole registered range

> A memory corruption vulnerability in the Linux kernel's nouveau driver allows local attackers to execute arbitrary code or escalate privileges due to incorrect VRAM buffer sizing.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2026
- **Updated:** 24 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-98518, GHSA-84w9-cx8r-cxrf, UBUNTU-CVE-2026-98518

## What is CVE-2026-98518?

CVE-2026-98518 is a high-severity memory corruption vulnerability in Linux, published on 18 Oct 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/nouveau/dmem: pin VRAM for the whole registered range

Commit c32287471077 ("gpu/drm/nouveau: enable THP support for GPU memory
migration") grew the device-private region that
nouveau_dmem_chunk_alloc() registers from DMEM_CHUNK_SIZE to
DMEM_CHUNK_SIZE * NR_CHUNKS, but left the VRAM buffer object backing that
region at DMEM_CHUNK_SIZE.

nouveau_dmem_page_addr() returns chunk->bo->offset plus the page's offset
within the registered region, so every page past the first chunk resolves
to VRAM outside the buffer object.

Size the buffer object to the region it backs.

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


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

Apply the vendor's patch.

## Is CVE-2026-98518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-98518 is a high-severity memory corruption vulnerability in Linux, published on 18 Oct 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-98518 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-98518/ (Markdown: https://insights.sbomify.com/CVE-2026-98518/index.md)
```

## Sources

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

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