drm/nouveau: unsubscribe the channel-kill event before the fence context
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e, Kernel 1fef7553dc628295c1208a4f2ac2094c62886e5d, Kernel 511585987d27d8cb668acebd399fc4deda23404c and 8 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e, >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <1fef7553dc628295c1208a4f2ac2094c62886e5d, >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <511585987d27d8cb668acebd399fc4deda23404c, >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <5db663fbff7b88aeeeecaf5220e177e524165101, >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <ee1cfb1acdff3fe3b47de7c536e5c77443c8e74f, >=ea13e5abf807ea912ce84eef6a1946b9a38c6508 <f3830fdd6930e233d727f29eee1617f7e6a0e9e5, =5.6 | f5a79a9ebfbafb87ca7a896e8d6b5f33a98d097e, 1fef7553dc628295c1208a4f2ac2094c62886e5d, 511585987d27d8cb668acebd399fc4deda23404c, 5db663fbff7b88aeeeecaf5220e177e524165101, ee1cfb1acdff3fe3b47de7c536e5c77443c8e74f, f3830fdd6930e233d727f29eee1617f7e6a0e9e5 |
| linux-kernel: Kernel | >=6.13.0 <6.18.51, >=6.19.0 <7.2.5, >=6.2.0 <6.6.160, >=6.7.0 <6.12.110, >=5.6.0 <6.1.191 | 6.18.51, 7.2.5, 6.6.160, 6.12.110, 6.1.191 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket