CVE-2026-64358
Last modified
CVE-2026-64358 is a medium-severity vulnerability rated 5.5/10 on the CVSS scale. 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
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| 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 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-64358?
How severe is CVE-2026-64358?
How do I fix CVE-2026-64358?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-64352In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64353In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64354In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64355In the Linux kernel, the following vulnerability has been re…9.8
- CVE-2026-64356In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64357In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64359In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64360In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-64361In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64362In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64363In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-64364In the Linux kernel, the following vulnerability has been re…8.8
Are you affected by CVE-2026-64358?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
