Strix
26.1K

CVE-2026-64358

UnknownEPSS 0.17%

Last modified

CVE-2026-64358 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.17% chance of exploitation in the next 30 days.

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.

Metrics

EPSS Probability
0.17%

6.4th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

Source: CNA advisory (CVE.org). NVD analysis pending.

VendorProductVersions
LinuxLinux>= 2209fdae5c2f615930c9af1379c1cfca199ec5d8, < 0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9; >= 0498b27a1542021d90269d58347501d4c3ccd84e, < ac0774961a6ea174a71d4ffa39966edafbf7662d; >= 26506a30e0e26d612f82a7bf0e395626968a44e6, < 973408ceab14555a8548b97c8cc7b54208c3f251; >= 34c519feef3e4fcff1078dc8bdb25fbbbd10303f, < 4c4b4af4a9f278da096f0dbdb6b59594701d29bf; >= 34c519feef3e4fcff1078dc8bdb25fbbbd10303f, < b1845a227fda37b2fe5327df3ca0015d7e290235; e78c39f720679fcf3a2eacd82725ec3ea2648301; >= 6.6.140, < 6.6.145; >= 6.12.86, < 6.12.96; >= 6.18.27, < 6.18.39; >= 7.0.4, < 7.1
LinuxLinux7.1

References

Timeline

Published
Last Modified
Status
Awaiting Analysis

Frequently Asked Questions

What is 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.
How severe is CVE-2026-64358?
Severity scoring for CVE-2026-64358 is pending analysis. The EPSS model estimates a 0.17% probability of exploitation in the next 30 days.
How do I fix CVE-2026-64358?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-64358?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST