drm/nouveau: unsubscribe the channel-kill event before the fence context
CVE-2026-89803 · published 16 Sept 2026
How serious is it
- Severity: high, CVSS score 7.8 out of 10.
- No exploit prediction (EPSS) score yet.
- Not on the CISA list of exploited vulnerabilities.
- No public exploit in Exploit-DB.
Is your app affected by CVE-2026-89803?
Paste this prompt into Claude Code, Cursor or any AI coding tool: it runs a free Shippable scan of your project and fixes what it finds. Built with Lovable, Bolt or v0? Scan your live app. Or upload your package file.
Who is affected
- Linux Linux: ea13e5abf807ea912ce84eef6a1946b9a38c6508 to < 5db663fbff7b88aeeeecaf5220e177e524165101, ea13e5abf807ea912ce84eef6a1946b9a38c6508 to < f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e, ea13e5abf807ea912ce84eef6a1946b9a38c6508 to < f3830fdd6930e233d727f29eee1617f7e6a0e9e5, ea13e5abf807ea912ce84eef6a1946b9a38c6508 to < 1fef7553dc628295c1208a4f2ac2094c62886e5d
- Linux Linux: 5.6
How to check
- Find out whether you run the affected product and which version, then compare it with the versions above.
How to fix
Copies a prompt for Claude Code, Cursor or Codex that asks it to check whether you run this product.
- Apply the vendor's update or mitigation from the references below. If there is none yet, limit exposure of the affected service until there is.
- If a vulnerable version was live, check your logs and rotate the secrets that server could read.
The advisory
In the Linux kernel, the following vulnerability has been resolved:
drm/nouveau: unsubscribe the channel-kill event before the fence context
nouveau_channel_del() tears the fence context down first and only drops
the channel-kill subscription later, in the middle of the nvif object
teardown:
if (chan->fence)
nouveau_fence(chan->cli->drm)->context_del(chan);
...
nvif_object_dtor(&chan->vram);
nvif_event_dtor(&chan->kill);
The subscribed handler is nouveau_channel_killed(), which calls
nouveau_channel_kill() and from there nouveau_fence_context_kill() on
chan->fence. A kill event delivered in that window takes fctx->lock and
walks fctx->pending on a fence context that context_del() has already
freed.
Nothing reaches this below Fermi today, because the subscription is
gated on FERMI_CHANNEL_GPFIFO and nothing kills a channel there. On
Fermi and newer the window is real but narrow, since a kill has to land
exactly while the channel is being destroyed. That is reason enough on
its own, which is why this carries a Fixes: tag. The last patch in this
series subscribes Tesla channels as well; nothing kills those today, so
it does not widen the exposure now, but it is the groundwork for a
recovery path that would, and the ordering is better fixed before that
lands than alongside it.
Drop the subscription before anything it depends on is torn down.
Check your whole app
Dependencies are only half of it. Free and read-only: before you push, run npx shippable-dev scan localhost:3000 in your project folder, no account needed. For your live app, you prove it's yours with a one-line tag first.
References
- git.kernel.org/stable/c/5db663fbff7b88aeeeecaf5220e177e524165101
- git.kernel.org/stable/c/f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e
- git.kernel.org/stable/c/f3830fdd6930e233d727f29eee1617f7e6a0e9e5
- git.kernel.org/stable/c/1fef7553dc628295c1208a4f2ac2094c62886e5d
- git.kernel.org/stable/c/511585987d27d8cb668acebd399fc4deda23404c
Merged from CVE List. Last updated 26 Oct 2026. All vulnerabilities · RSS · JSON