What’s Vulnerable › Vulnerabilities
CVE-2026-64358: media: mtk-jpeg: cancel workqueue on release for supported platforms only
- Severity: medium (CVSS 5.5 v3.1)
- Exploited in the wild: not listed in CISA KEV
- EPSS: 0.1% probability of exploitation in the next 30 days
- Public exploit or detection template: none known
- Published: 2026-07-25 · updated 2026-09-04
- Weakness: CWE-476
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.
Affected products
- Linux kernel: from 6.6.140 before 6.6.145; from 6.12.86 before 6.12.96; from 6.18.27 before 6.18.39; from 7.0.4 before 7.1.4 — fixed in 6.12.96, 6.18.39, 6.6.145, 7.1.4
How to fix
Upgrade to a fixed version: Linux kernel 6.12.96, 6.18.39, 6.6.145, 7.1.4. Check the vendor advisory for mitigations.
References
- https://git.kernel.org/stable/c/0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9
- https://git.kernel.org/stable/c/4c4b4af4a9f278da096f0dbdb6b59594701d29bf
- https://git.kernel.org/stable/c/973408ceab14555a8548b97c8cc7b54208c3f251
- https://git.kernel.org/stable/c/ac0774961a6ea174a71d4ffa39966edafbf7662d
- https://git.kernel.org/stable/c/b1845a227fda37b2fe5327df3ca0015d7e290235
Get alerted when CVE-2026-64358 or the next vulnerability affects your stack