CVE-2026-64358: media: mtk-jpeg: cancel workqueue on release for supported platforms only
Noroxi assessment
Priority: Monitor (action score 22/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Linux Linux 0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9, 4c4b4af4a9f278da096f0dbdb6b59594701d29bf, 6.12.96.
Low priority for now. Upgrade to Linux Linux 0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9, 4c4b4af4a9f278da096f0dbdb6b59594701d29bf, 6.12.96 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 25, 2026
- Updated
- Sep 4, 2026
- EPSS
- 0.1% · 1th percentile
- CWE
- CWE-476
Report tools
Action score
22
Monitor
Low priority for now.
- CVSS
- 22 / 40 · 5.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux | linux kernel | cpe:2.3:o:linux:linux_kernel |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux linux kernel6.6.140 and later · before 6.6.145
- linux linux kernel6.12.86 and later · before 6.12.96
- linux linux kernel6.18.27 and later · before 6.18.39
- linux linux kernel7.0.4 and later · before 7.1.4
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- e78c39f720679fcf3a2eacd82725ec3ea2648301, 7.1affected
- 2209fdae5c2f615930c9af1379c1cfca199ec5d8 and later · before 0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9affected · git
- 0498b27a1542021d90269d58347501d4c3ccd84e and later · before ac0774961a6ea174a71d4ffa39966edafbf7662daffected · git
- 26506a30e0e26d612f82a7bf0e395626968a44e6 and later · before 973408ceab14555a8548b97c8cc7b54208c3f251affected · git
- 34c519feef3e4fcff1078dc8bdb25fbbbd10303f and later · before 4c4b4af4a9f278da096f0dbdb6b59594701d29bfaffected · git
- 34c519feef3e4fcff1078dc8bdb25fbbbd10303f and later · before b1845a227fda37b2fe5327df3ca0015d7e290235affected · git
- 6.6.140 and later · before 6.6.145affected · semver
- 6.12.86 and later · before 6.12.96affected · semver
- 6.18.27 and later · before 6.18.39affected · semver
- 7.0.4 and later · before 7.1affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux-6.12 | before 6.12.100-1~deb12u1 | 6.12.100-1~deb12u1 |
| Debian:13 | linux | before 6.12.96-1 | 6.12.96-1 |
| Debian:14 | linux | before 7.1.4-1 | 7.1.4-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-31431crypto: algif_aead - Revert to operating out-of-placeKEV90Now
- CVE-2022-0847A flaw was found in the way the "flags" member of the new pipe buffer structure was lacking proper initialization in copy_page_to_iter_pipe KEV89Now
- CVE-2021-22555Heap Out-Of-Bounds Write in Netfilter IP6T_SO_SET_REPLACEKEV85Now
Published before and after this one in the same product
- ← EarlierCVE-2026-64356Jul 25, 2026 · xfs: fix memory leak in xfs_dqinode_metadir_create()22Monitor
- ← EarlierCVE-2026-64357Jul 25, 2026 · xfs: fix exchmaps reservation limit check22Monitor
- Later →CVE-2026-64359Jul 25, 2026 · nilfs2: reject CLEAN_SEGMENTS ioctl with out-of-range segment numbers22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 0fed0fc34ce734b4b8c2f6a467d38bddcb21dda9 | Vendor (CNA) |
| Linux Linux | 4c4b4af4a9f278da096f0dbdb6b59594701d29bf | Vendor (CNA) |
| Linux Linux | 6.12.96 | Vendor (CNA) |
| Linux Linux | 6.18.39 | Vendor (CNA) |
| Linux Linux | 6.6.145 | Vendor (CNA) |
| Linux Linux | 7.1 | Vendor (CNA) |
| Linux Linux | 973408ceab14555a8548b97c8cc7b54208c3f251 | Vendor (CNA) |
| Linux Linux | ac0774961a6ea174a71d4ffa39966edafbf7662d | Vendor (CNA) |
| Linux Linux | b1845a227fda37b2fe5327df3ca0015d7e290235 | Vendor (CNA) |
| debian:linux | 6.12.96-1 · Debian:13 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.100-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-476 · NULL Pointer DereferenceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.