media: imx-jpeg: cancel timeout worker when streaming stops
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel 9e393784a902bb4eb00a21e46d389a32c7ea61b0, Kernel 6.2, Kernel 49a0623994a10d3d333d48c304f89d816495f332 and 5 more.
In the Linux kernel, the following vulnerability has been resolved: media: imx-jpeg: cancel timeout worker when streaming stops Each per-fd context ctx owns a delayed_work (ctx->task_timer, callback mxc_jpeg_device_run_timeout) armed via schedule_delayed_work() at the end of mxc_jpeg_device_run() to recover a stalled encode/decode job. The only existing cancellation is cancel_delayed_work() in the frame-done IRQ handler, which de-queues a pending work item but does not wait for a callback that has already started, and it only runs when a frame completes. When the fd is closed while a job is in flight (the frame-done IRQ has not fired yet), nothing syncs the worker before mxc_jpeg_release() frees ctx with kfree() after v4l2_m2m_ctx_release(). A queued or executing mxc_jpeg_device_run_timeout() can then recover ctx through container_of(&ctx->task_timer) and dereference it (ctx->mxc_jpeg, slot_data, dev_warn) after ctx has been freed. Cancel the worker from mxc_jpeg_stop_streaming(). The cancel cannot live in mxc_jpeg_release(): mxc_jpeg_device_run() arms the timer while holding only hw_lock, not the mxc_jpeg->lock mutex that release holds, so a cancel in release could still race a concurrent mxc_jpeg_device_run() that re-arms the timer afterwards. mxc_jpeg_stop_streaming() instead runs inside v4l2_m2m_ctx_release() -> vb2_queue_release(), i.e. after v4l2_m2m_cancel_job() has set TRANS_ABORT and waited for any in-flight job to finish (so __v4l2_m2m_try_queue() will not queue and v4l2_m2m_try_run() will not run any further job for this context, which prevents mxc_jpeg_device_run() from re-arming the timer) and before the m2m context is freed. cancel_delayed_work_sync() removes a pending work item and waits for a running callback, so the worker can no longer race with the subsequent kfree(). The cancel is placed before the buffer-release loop so a concurrently running timeout callback cannot race with it over the same buffers. If the frame-done IRQ canceled a still-pending timer, this cancel is a no-op; if the timeout callback has already started, it waits for the callback to finish. The same mxc_jpeg_stop_streaming() call is also reached from VIDIOC_STREAMOFF, which drains the worker early, although STREAMOFF itself does not free ctx -- the use-after-free arises only when the fd is later closed. This bug was found by static analysis.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| Linux | Kernel | >=cfed9632ca8e8bdf0128745ae2400b72c4292886 <9e393784a902bb4eb00a21e46d389a32c7ea61b0, >=6.1.143 <6.2, >=cfed9632ca8e8bdf0128745ae2400b72c4292886 <49a0623994a10d3d333d48c304f89d816495f332, >=cfed9632ca8e8bdf0128745ae2400b72c4292886 <77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341, >=cfed9632ca8e8bdf0128745ae2400b72c4292886 <78fdfbf117c409273eecbfa7a528ef42358a0e38, =1f3367fa4210f37417cd55622b3872ababd2f06d, =6.2 | 9e393784a902bb4eb00a21e46d389a32c7ea61b0, 6.2, 49a0623994a10d3d333d48c304f89d816495f332, 77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341, 78fdfbf117c409273eecbfa7a528ef42358a0e38 |
| linux-kernel: Kernel | >=6.13.0 <6.18.61, >=6.19.0 <7.3.2, >=6.2.0 <6.12.117, >=6.1.143 <6.2 | 6.18.61, 7.3.2, 6.12.117, 6.2 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in Kernel, strongest first
Embed
A live severity badge for an advisory, README or ticket