Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-64358media: mtk-jpeg: cancel workqueue on release for supported platforms only

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.

Timeline

  1. ID reserved

    By Linux

  2. · 6 days later

    Published

  3. · 23 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

CVSS scores of CVE-2026-64358, by who scored it
Scored byCVSSScoreVector
NVDNVD · Analyzed3.1Medium5.5CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
EPSS (exploitation in 30 days)
0.12% · top 98% of all CVEs (14 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Medium 5.5.

Affected products

  • Linux · Linux

    • affected 2209fdae5c2f615930c9af1379c1cfca199ec5d8 – < 0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9
    • affected 0498b27a1542021d90269d58347501d4c3ccd84e – < ac0774961a6ea174a71d4ffa39966edafbf7662d
    • affected 26506a30e0e26d612f82a7bf0e395626968a44e6 – < 973408ceab14555a8548b97c8cc7b54208c3f251
    • affected 34c519feef3e4fcff1078dc8bdb25fbbbd10303f – < 4c4b4af4a9f278da096f0dbdb6b59594701d29bf
    • affected 34c519feef3e4fcff1078dc8bdb25fbbbd10303f – < b1845a227fda37b2fe5327df3ca0015d7e290235
    • affected e78c39f720679fcf3a2eacd82725ec3ea2648301
    • affected 6.6.140 – < 6.6.145
    • affected 6.12.86 – < 6.12.96
    • affected 6.18.27 – < 6.18.39
    • affected 7.0.4 – < 7.1
  • Linux · Linux

    • affected 7.1
    • unaffected < 7.1
    • unaffected 6.6.145 – ≤ 6.6.*
    • unaffected 6.12.96 – ≤ 6.12.*
    • unaffected 6.18.39 – ≤ 6.18.*
    • unaffected 7.1.4 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References5

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-64358 badge
[![CVE-2026-64358](https://cveledger.app/badge/CVE-2026-64358.svg)](https://cveledger.app/cve/CVE-2026-64358)

Record last updated .