Linux
drm/nouveau: unsubscribe the channel-kill event before the fence context
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= ea13e5abf807ea912ce84eef6a1946b9a38c6508, < ee1cfb1acdff3fe3b47de7c536e5c77443c8e74f
- >= ea13e5abf807ea912ce84eef6a1946b9a38c6508, < 5db663fbff7b88aeeeecaf5220e177e524165101
- >= ea13e5abf807ea912ce84eef6a1946b9a38c6508, < f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e
- >= ea13e5abf807ea912ce84eef6a1946b9a38c6508, < f3830fdd6930e233d727f29eee1617f7e6a0e9e5
- >= ea13e5abf807ea912ce84eef6a1946b9a38c6508, < 1fef7553dc628295c1208a4f2ac2094c62886e5d
- >= ea13e5abf807ea912ce84eef6a1946b9a38c6508, < 511585987d27d8cb668acebd399fc4deda23404c
Fixed in ee1cfb1acdff3fe3b47de7c536e5c77443c8e74f, 5db663fbff7b88aeeeecaf5220e177e524165101, f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e, f3830fdd6930e233d727f29eee1617f7e6a0e9e5, 1fef7553dc628295c1208a4f2ac2094c62886e5d, 511585987d27d8cb668acebd399fc4deda23404c
- 5.6
Fixed in 0, 6.1.191, 6.6.160, 6.12.110, 6.18.51, 7.2.5, 7.3
Mitigation
Upgrade Linux to ee1cfb1acdff3fe3b47de7c536e5c77443c8e74f or 5db663fbff7b88aeeeecaf5220e177e524165101 or f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e or f3830fdd6930e233d727f29eee1617f7e6a0e9e5 or 1fef7553dc628295c1208a4f2ac2094c62886e5d or 511585987d27d8cb668acebd399fc4deda23404c or later.
Upgrade Linux to 0 or 6.1.191 or 6.6.160 or 6.12.110 or 6.18.51 or 7.2.5 or 7.3 or later.
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.