CVE-2026-46011
Last modified
CVE-2026-46011 is a high-severity vulnerability rated 7.8/10 on the CVSS scale. 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). EPSS estimates a 0.13% chance of exploitation in the next 30 days.
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.
Metrics
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux Kernel | >= 6.2, < 6.6.140 |
| Linux | Linux Kernel | >= 6.7, < 6.12.86 |
| Linux | Linux Kernel | >= 6.13, < 6.18.27 |
| Linux | Linux Kernel | >= 6.19, < 7.0.4 |
References
Timeline
- Published
- Last Modified
- Status
- Analyzed
Frequently Asked Questions
What is CVE-2026-46011?
How severe is CVE-2026-46011?
How do I fix CVE-2026-46011?
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-46006In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46007In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46008In the Linux kernel, the following vulnerability has been re…4.7
- CVE-2026-46009In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-4601Versions of the package jsrsasign before 11.1.1 are vulnerab…9.1
- CVE-2026-46010In the Linux kernel, the following vulnerability has been re…8.1
- CVE-2026-46012In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46013In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46014In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46015In the Linux kernel, the following vulnerability has been re…7.8
- CVE-2026-46016In the Linux kernel, the following vulnerability has been re…5.5
- CVE-2026-46017In the Linux kernel, the following vulnerability has been re…4.7
Are you affected by CVE-2026-46011?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
