CVE-2026-46011media: mtk-jpeg: fix use-after-free in release path due to uncancelled work
- 7.8HighCVSS base score
- 0.13%Exploitation in 30 daysEPSS · top 98% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- NonePublic exploitsnone known yet
Description
In the Linux kernel, the following vulnerability has been resolved: media: mtk-jpeg: fix use-after-free in release path due to uncancelled work The mtk_jpeg_release() function frees the context structure (ctx) without first cancelling any pending or running work in ctx->jpeg_work. This creates a race window where the workqueue callback may still be accessing the context memory after it has been freed. Race condition: CPU 0 (release) CPU 1 (workqueue) ---------------- ------------------ close() mtk_jpeg_release() mtk_jpegenc_worker() ctx = work->data // accessing ctx kfree(ctx) // freed! access ctx // UAF! The work is queued via queue_work() during JPEG encode/decode operations (via mtk_jpeg_device_run). If the device is closed while work is pending or running, the work handler will access freed memory. Fix this by calling cancel_work_sync() BEFORE acquiring the mutex. This ordering is critical: if cancel_work_sync() is called after mutex_lock(), and the work handler also tries to acquire the same mutex, it would cause a deadlock. Note: The open error path does NOT need cancel_work_sync() because INIT_WORK() only initializes the work structure - it does not schedule it. Work is only scheduled later during ioctl operations.
Timeline
ID reserved
By Linux
- 14 days later
· 14 days later
Published
- 2 months later
· 2 months 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
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| LinuxCNA (assigner) | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVDNVD · Analyzed | 3.1 | High7.8 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
- EPSS (exploitation in 30 days)
- 0.13% · top 98% of all CVEs (20 Nov 2026)
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.8.
Affected products
- affected 5fb1c2361e5630491d2a2f9359654eb022601bc0 – < 2209fdae5c2f615930c9af1379c1cfca199ec5d8
- affected 5fb1c2361e5630491d2a2f9359654eb022601bc0 – < 0498b27a1542021d90269d58347501d4c3ccd84e
- affected 5fb1c2361e5630491d2a2f9359654eb022601bc0 – < 26506a30e0e26d612f82a7bf0e395626968a44e6
- affected 5fb1c2361e5630491d2a2f9359654eb022601bc0 – < e78c39f720679fcf3a2eacd82725ec3ea2648301
- affected 5fb1c2361e5630491d2a2f9359654eb022601bc0 – < 34c519feef3e4fcff1078dc8bdb25fbbbd10303f
- affected 6.2
- unaffected < 6.2
- unaffected 6.6.140 – ≤ 6.6.*
- unaffected 6.12.86 – ≤ 6.12.*
- unaffected 6.18.27 – ≤ 6.18.*
- unaffected 7.0.4 – ≤ 7.0.*
- unaffected 7.1 – ≤ *
References
References5
- https://git.kernel.org/stable/c/2209fdae5c2f615930c9af1379c1cfca199ec5d8 (opens in a new tab)
- https://git.kernel.org/stable/c/0498b27a1542021d90269d58347501d4c3ccd84e (opens in a new tab)
- https://git.kernel.org/stable/c/26506a30e0e26d612f82a7bf0e395626968a44e6 (opens in a new tab)
- https://git.kernel.org/stable/c/e78c39f720679fcf3a2eacd82725ec3ea2648301 (opens in a new tab)
- https://git.kernel.org/stable/c/34c519feef3e4fcff1078dc8bdb25fbbbd10303f (opens in a new tab)
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-32308 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisories (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-46011)Record last updated .