# CVE-2026-99468: media: imx-jpeg: cancel timeout worker when streaming stops

Status: published. Published: 2026-11-19. Updated: 2026-11-22.

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.

## Remediation

No remediation reported in collected sources

## Affected products and versions

- Linux / Linux: ≥ cfed9632ca8e8bdf0128745ae2400b72c4292886; < 77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341 (affected, git); ≥ cfed9632ca8e8bdf0128745ae2400b72c4292886; < 49a0623994a10d3d333d48c304f89d816495f332 (affected, git); ≥ cfed9632ca8e8bdf0128745ae2400b72c4292886; < 9e393784a902bb4eb00a21e46d389a32c7ea61b0 (affected, git); ≥ cfed9632ca8e8bdf0128745ae2400b72c4292886; < 78fdfbf117c409273eecbfa7a528ef42358a0e38 (affected, git); 1f3367fa4210f37417cd55622b3872ababd2f06d (affected, git); ≥ 6.1.143; < 6.2 (affected, semver). Source: CNA: Linux
- Linux / Linux: 6.2 (affected); ≥ 0; < 6.2 (unaffected, semver); ≥ 6.12.117; ≤ 6.12.* (unaffected, semver); ≥ 6.18.61; ≤ 6.18.* (unaffected, semver); ≥ 7.3.2; ≤ 7.3.* (unaffected, semver); ≥ 7.4-rc1; ≤ * (unaffected, original_commit_for_fix). Source: CNA: Linux

## Severity and prioritization

- CVSS 3.1: 7 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: CNA: Linux

- CVSS 3.1: 7 (high); CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H; source: NVD: 416baaa9-dc9f-4396-8d5f-8c081fb06d67

- CISA KEV: No listing in collected sources

- EPSS: 0.21% as of 2026-11-21; percentile 11.04%

- SSVC: Not available

- Weaknesses: Not reported

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://git.kernel.org/stable/c/77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341 (CNA: Linux)

- https://git.kernel.org/stable/c/49a0623994a10d3d333d48c304f89d816495f332 (CNA: Linux)

- https://git.kernel.org/stable/c/9e393784a902bb4eb00a21e46d389a32c7ea61b0 (CNA: Linux)

- https://git.kernel.org/stable/c/78fdfbf117c409273eecbfa7a528ef42358a0e38 (CNA: Linux)

- https://git.kernel.org/stable/c/49a0623994a10d3d333d48c304f89d816495f332 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/77e1c41d65a9f3cd22d73d0ec1f33cf6cd37b341 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/78fdfbf117c409273eecbfa7a528ef42358a0e38 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

- https://git.kernel.org/stable/c/9e393784a902bb4eb00a21e46d389a32c7ea61b0 (416baaa9-dc9f-4396-8d5f-8c081fb06d67)

## Provenance

- CNA: Linux: https://www.cve.org/CVERecord?id=CVE-2026-99468; retrieved 2026-11-22; source updated 2026-11-22

- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-99468; retrieved 2026-11-22; source updated 2026-11-22

- FIRST EPSS: https://api.first.org/data/v1/epss?cve=CVE-2026-99468; retrieved 2026-11-22; source updated Not reported

Revision: fcc9cd389b344230889ce1ab31b3b9bd207ebd2824c1c4ef5891a50da3e87b55

Canonical: https://y2.dev/cve/CVE-2026-99468

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.