data built 2026-10-19T13:16:53Z

Look up another CVE · open CVE-2026-98518 in the interactive tracker

CVE-2026-98518

drm/nouveau/dmem: pin VRAM for the whole registered range

Published 2026-10-18 (today) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: unimportant.

Debian does not build this code. The per-release build detail is under "Where it lives" below.

What to do, per Debian release

Debian's own status for CVE-2026-98518 in every release this site tracks, and what each one means in practice. Every status below is the one the Debian Security Team publishes for this CVE. source

ReleaseStatus VersionWhat this means
Debian 12bookwormnot affected6.1.190-1Nothing to do. bookworm never shipped the vulnerable code.
Debian 13trixienot affected6.12.113-1Nothing to do. trixie never shipped the vulnerable code.
Debian 14forkyfixed7.2.9-1Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts.
Debian unstablesidfixed7.2.9-1Update the kernel and reboot. Fixed in 7.2.9-1. A running kernel keeps the old code until the machine restarts.

The vulnerability

What the bug is

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.

Where it lives

The fix touches these files. If the subsystem is one you do not use, the practical exposure is lower, though the package is still the vulnerable one.

drivers/gpu/drm/nouveau/nouveau_dmem.c

What this is
DRM DRIVER FOR NVIDIA GEFORCE/QUADRO GPUSMAINTAINERS section matched on drivers/gpu/drm/nouveau/ · dri-devel@lists.freedesktop.org · Supported
Kernel module
none to look for. The file would have gone into nouveau, and Debian does not compile it into that module, so finding nouveau in lsmod would say nothing about this CVE.

Check it on the machine

grep -wE 'CONFIG_DRM_NOUVEAU|CONFIG_DRM_NOUVEAU_SVM' /boot/config-$(uname -r)

Reads the booted kernel's own configuration, on the machine and nowhere else. =y is built in, =m is a module, and an is not set line means the code is not there.

Show whether Debian builds this, per release

Debian does not build this code. In 4 releases below, every kernel flavour Debian publishes has the switch off, so the vulnerable file is compiled into no kernel binary Debian ships.

  • bookworm, trixie, forky, sidn
n
not enabled on any flavour - this release does not build the code
Build switches
CONFIG_DRM_NOUVEAU, CONFIG_DRM_NOUVEAU_SVM
Reads as
all on means the file is compiled; any one off means it is not.

From the configuration Debian publishes for every kernel flavour it builds. It covers only the architectures Debian ships a linux-config package for, and nothing about a kernel you built yourself. Debian's own status above stays authoritative about the source package.MAINTAINERS kbuild Makefiles Debian linux-config packages

Signals

Published
2026-10-18 (today)source
CVSS
no vector published, unrated
Attack vector
not published
EPSS
not scored
CISA KEV
not listedthe KEV catalogue
Debian urgency
unimportantsource
Subsystem
drivers/gpu

Upstream fixes

The versions the CNA records as introducing and fixing this, and the commit for each. source

IntroducedFixed inCommit
6.197.2.906c69c64686a
6.197.364ca4cdd1031

Why the CNA scored it this way

The kernel CNA published no CVSS vector and no reasoning for CVE-2026-98518, which is why it is shown as unrated rather than given an invented score. 6,405 of the 20,413 CVEs here carry reasoning; this is not one of them.