CVE-2026-64358

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.

Package Linux Kernel
Published 2026-07-25
Last modified 2026-07-25
Patch available
Yes

Affected versions

Linux kernel versions 6.6.140, 6.12.86, 6.18.27, 7.0.4, 7.1 and later are affected. Fixed in 6.6.145, 6.12.96, 6.18.39, 7.1.4, 7.2-rc1 and their respective stable series.

Affected from
≥ 6.6.140 ≥ 6.12.86 ≥ 6.18.27 ≥ 7.0.4 ≥ 7.1
Fixed in
✓ 6.6.145 6.6.x ✓ 6.12.96 6.12.x ✓ 6.18.39 6.18.x ✓ 7.1.4 7.1.x ✓ 7.2-rc1

Frequently asked questions

  • What is CVE-2026-64358?

    CVE-2026-64358 is a unscored severity Linux kernel vulnerability . It affects Linux kernel versions from 6.6.140 onward and has been patched in 6.6.145, 6.12.96, 6.18.39 and others. CVE-2026-64358 has not been confirmed as actively exploited and is not listed in the CISA KEV catalog.

  • Is there a patch available for CVE-2026-64358?

    Yes. CVE-2026-64358 has been patched. Fixed versions include 6.6.145, 6.12.96, 6.18.39 and others. If you are running Linux kernel 6.6.140 or later up to the fix versions, apply the relevant patch for your kernel branch.

  • Is CVE-2026-64358 actively exploited?

    No. CVE-2026-64358 has not been confirmed as actively exploited. It is not listed in the CISA Known Exploited Vulnerabilities (KEV) catalog.