Look up another CVE · open CVE-2026-89553 in the interactive tracker
CVE-2026-89553
nouveau/gem: reserve the bo in the info ioctl around the vma lookup
Published 2026-09-11 (37 days ago) by the Linux kernel CNA. Subsystem drivers/gpu. Debian urgency: not yet assigned.
What to do, per Debian release
Debian's own status for CVE-2026-89553 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
| Release | Status | Version | What this means |
|---|---|---|---|
| Debian 12bookworm | vulnerable | 6.1.190-1 | No fix published anywhere yet, neither in Debian nor upstream for the series bookworm tracks. Watch the Debian tracker page for this CVE. Advisories for bookworm have historically landed a median of 23 days after publication. |
| Debian 13trixie | fixedDSA-6528-1 · 2026-09-29 · text | 6.12.111-1 | Update the kernel and reboot. DSA-6528-1 shipped the fix on 2026-09-29, in 6.12.111-1. A running kernel keeps the old code until the machine restarts. |
| Debian 14forky | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian unstablesid | fixed | 7.2.6-1 | Update the kernel and reboot. Fixed in 7.2.6-1. A running kernel keeps the old code until the machine restarts. |
| Debian 12bookworm · linux-6.12 | fixedDLA-4817-1 · 2026-10-04 · text | 6.12.111-1~deb12u1 | Update the kernel and reboot. DLA-4817-1 shipped the fix on 2026-10-04, in 6.12.111-1~deb12u1. A running kernel keeps the old code until the machine restarts. |
The vulnerability
What the bug is
In the non-uvmm path, there could be a race between the info lookup finding the vma, and the gem close path closing the vma leading to a use-after-free. Spotted with the help of Opus 4.6.
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_gem.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
- nouveau
Check it on the machine
grep -w CONFIG_DRM_NOUVEAU /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.
lsmod | grep -w nouveauPrints a line if that module is loaded right now, and nothing if it is not. One that is not loaded can still be loaded later by anything that needs it.
Show whether Debian builds this, per release
Debian builds this, but not on every flavour. At least one release below builds the code on some of its kernel flavours and not on others, so the answer depends on the architecture and flavour installed.
- bookwormMnot built on amd64/cloud-amd64, arm64/cloud-arm64
- trixieMnot built on amd64/cloud-amd64, arm64/cloud-arm64, armel/rpi, s390x/s390x
- forky, sidMnot built on amd64/cloud-amd64, arm64/cloud-arm64, s390x/s390x
- bookworm · linux-6.12Mnot built on amd64/cloud-amd64, arm64/cloud-arm64
- M
- a module where it is built at all; some flavours do not build it
- Build switch
- CONFIG_DRM_NOUVEAU
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-09-11 (37 days ago)source
- CVSS
- 7.8 high
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:Hsource recompute it - Attack vector
- local (AV:L)source
- EPSS
- 0.13%, higher than 2.6% of all CVEssource
- CISA KEV
- not listedthe KEV catalogue
- Debian urgency
- not yet assignedsource
- Subsystem
- drivers/gpu
Upstream fixes
The versions the CNA records as introducing and fixing this, and the commit for each. source
| Introduced | Fixed in | Commit |
|---|---|---|
| 3.1 | 6.6.157 | e05c28bd6043 |
| 3.1 | 6.12.109 | 208867763843 |
| 3.1 | 6.18.50 | ff110e85837d |
| 3.1 | 7.2.4 | e60466011ac3 |
| 3.1 | 7.3 | 5e17160d41d9 |
Debian advisories
| Advisory | Date | Shipped to | Debian |
|---|---|---|---|
| DLA-4817-1 | 2026-10-04 | bookworm 6.12.111-1~deb12u1 | tracker |
| DSA-6528-1 | 2026-09-29 | trixie 6.12.111-1 | tracker |
Why the CNA scored it this way
Quoted from the kernel CNA's own scoring file, word for word. A highlighted metric carries the most severe value CVSS v3.1 defines for it, which is what pushes the score up. source
- AV:LAttack vector, local
- Reached only via local DRM ioctls on a nouveau render node (/dev/dri/renderD*): DRM_IOCTL_NOUVEAU_GEM_INFO (nouveau_gem_ioctl_info→nouveau_gem_info) racing DRM_IOCTL_GEM_CLOSE (nouveau_gem_object_close). Not reachable from network protocols, adjacent radios, or physical buses.
- AC:LAttack complexity, low
- The attacker controls both sides of the race with threads that GEM_INFO and GEM_CLOSE the same handle, so close kfree()s the nouveau_vma while info still uses it. Skipping UVMM (legacy GEM_NEW) selects the vulnerable path; no victim timing or rare config is required.
- PR:LPrivileges required, low
- NOUVEAU_GEM_INFO and GEM_CLOSE are DRM_RENDER_ALLOW with no DRM_ROOT_ONLY or capability checks. Any unprivileged local user who can open the nouveau render node (typical render/video group or uaccess ACL) can trigger it without init-namespace root.
- UI:NUser interaction, none
- Exploitation needs only the attacker opening their own DRM client, creating a GEM BO, and racing GEM_INFO against GEM_CLOSE on that handle; no separate victim action is required.
- S:UScope, unchanged
- The use-after-free corrupts kernel heap state (struct nouveau_vma) inside the host nouveau driver. Impact stays in the same kernel authority; this is not a VM escape or IOMMU/DMA isolation bypass.
- C:HConfidentiality impact, high
- Use-after-free of struct nouveau_vma lets GEM_INFO read vma->addr after kfree, and concurrent walks of nvbo->vma_list can follow attacker-reused slab objects, enabling kernel memory disclosure as with other UAFs.
- I:HIntegrity impact, high
- UAF of the VMA plus concurrent list_del/list_del_init on nvbo->vma_list enables heap spraying and list-pointer corruption, supporting arbitrary kernel writes and control-flow hijack as with other kernel UAFs.
- A:HAvailability impact, high
- Dereferencing a freed nouveau_vma in GEM_INFO or walking a concurrently deleted vma_list causes a kernel oops/panic; the attacker can repeat the race to crash or hang the system.