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 mtkjpegrelease function cancels any pending or running work present in the driver workqueue using cancelworksync function. Currently, only the multicore based variants use this workqueue and they have the jpegworker platform data field initialized with a workqueue callback function. For the others, this field value remain NULL by default. The cancelworksync function is unconditionally called in mtkjpegrelease function, even for the variants that do not use the workqueue. This call generates a WARNON print in __flush_work because the workqueue callback function presence check fails in _flushwork function (used by cancelworksync).
So, to avoid these warnings, call cancelworksync only if a workqueue callback is defined in platform data.
{
"cna_assigner": "Linux",
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/64xxx/CVE-2026-64358.json"
}