CVEvulnerability
CVE-2026-64358
5.5 MEDIUM
Official page ↗
- Status
- Analyzed
- Published
- 2026-07-25
- Last modified
- 2026-09-04
- Assigner
- 416baaa9-dc9f-4396-8d5f-8c081fb06d67
- CVSS 3.1 ([email protected])
- 5.5 MEDIUM — CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
- Weaknesses
- 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 configurations
• linux linux kernel (>= 6.6.140 < 6.6.145)
• linux linux kernel (>= 6.12.86 < 6.12.96)
• linux linux kernel (>= 6.18.27 < 6.18.39)
• linux linux kernel (>= 7.0.4 < 7.1.4)
Related
Weakness · CWE (1)
- CWE-476 NULL Pointer Dereference weakness
References
- https://git.kernel.org/stable/c/0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9 Patch
- https://git.kernel.org/stable/c/4c4b4af4a9f278da096f0dbdb6b59594701d29bf Patch
- https://git.kernel.org/stable/c/973408ceab14555a8548b97c8cc7b54208c3f251 Patch
- https://git.kernel.org/stable/c/ac0774961a6ea174a71d4ffa39966edafbf7662d Patch
- https://git.kernel.org/stable/c/b1845a227fda37b2fe5327df3ca0015d7e290235 Patch