CVE-2023-52491

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2024-03-11. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 0

A fix is available — apply it.

In the Linux kernel, the following vulnerability has been resolved:

media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run

In mtk_jpeg_probe, &jpeg->job_timeout_work is bound with mtk_jpeg_job_timeout_work.

In mtk_jpeg_dec_device_run, if error happens in mtk_jpeg_set_dec_dst, it will finally start the worker while mark the job as finished by invoking v4l2_m2m_job_finish.

There are two methods to trigger the bug. If we remove the module, it which will call mtk_jpeg_remove to make cleanup. The possible sequence is as follows, which will cause a use-after-free bug.

CPU0 CPU1 mtk_jpeg_dec_... | start worker | |mtk_jpeg_job_timeout_work mtk_jpeg_remove | v4l2_m2m_release | kfree(m2m_dev); | | | v4l2_m2m_get_curr_priv | m2m_dev->curr_ctx //use

If we close the file descriptor, which will call mtk_jpeg_release, it will have a similar sequence.

Fix this bug by starting timeout worker only if started jpegdec worker successfully. Then v4l2_m2m_job_finish will only be called in either mtk_jpeg_job_timeout_work or mtk_jpeg_dec_device_run.

CVSS v3
7.8
EG Score
7.8(medium)
EG Risk
35(Track)
EG Risk 35/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

March 11, 2024

Last Modified

August 5, 2026

Advisory Details (6)

Auto-updated Aug 4, 2026
No patch confirmed yet.
generic

media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6e2f37022f0fc0893da4d85a0500c9d547fffd4c
generic

media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/43872f44eee6c6781fea1348b38885d8e78face9
generic

media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/206c857dd17d4d026de85866f1b5f0969f2a109e
generic

media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1b1036c60a37a30caf6759a90fe5ecd06ec35590
generic

media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/9fec4db7fff54d9b0306a332bab31eac47eeb5f6
generic

media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/8254d54d00eb6cdb8367399c7f912eb8d354ecd7

Patch Availability(14)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-20.04-edge (5.15.0.106.106) @ jammy2026-05-23ubuntu
ubuntulinux-tools-intel-iotg (5.15.0.1057.57) @ jammy2026-05-23ubuntu
ubuntulinux-tools-aws-lts-22.04 (5.15.0.1061.61) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.5.0.41.41) @ mantic2026-05-23ubuntu
ubuntulinux-tools-raspi-nolpae (5.15.0.1054.52) @ jammy2026-05-23ubuntu
ubuntulinux-tools-starfive (6.5.0.1015.17) @ mantic2026-05-23ubuntu
ubuntulinux-tools-oem-22.04d (6.5.0.1024.26) @ jammy2026-05-23ubuntu
ubuntulinux-virtual-hwe-22.04 (6.5.0.41.41~22.04.2) @ jammy2026-05-23ubuntu
ubuntulinux-tools-laptop-23.10 (6.5.0.1017.20) @ mantic2026-05-23ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.5.0.1021.29) @ jammy2026-05-23ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.26) @ mantic2026-05-23ubuntu
ubuntulinux-tools-intel-iotg-edge (5.15.0.1058.64~20.04.1) @ focal2026-05-23ubuntu
ubuntulinux-tools-oracle-64k (6.5.0.1024.24~22.04.1) @ jammy2026-05-23ubuntu
linuxKernel @ 5.10.210—osv

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(13)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 14× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 124 total refreshes for this CVE.

  1. 2026-08-07 16:25 UTCEPSS rescore
  2. 2026-08-06 13:45 UTCEPSS rescore
  3. 2026-08-05 19:15 UTCEPSS rescore
  4. 2026-08-05 19:15 UTCEPSS rescore
  5. 2026-08-05 09:43 UTCEG score recompute
  6. 2026-08-05 09:43 UTCGHSA enrichment
  7. 2026-08-04 12:20 UTCEG score recompute
  8. 2026-08-04 12:20 UTCVendor advisory
  9. 2026-08-04 12:20 UTCGHSA enrichment
  10. 2026-08-04 10:36 UTCEPSS rescore
  11. 2026-08-04 09:53 UTCEG score recompute
  12. 2026-08-04 09:53 UTCVendor advisory
  13. 2026-08-04 09:53 UTCGHSA enrichment
  14. 2026-08-03 10:34 UTCEPSS rescore
  15. 2026-08-01 04:14 UTCEPSS rescore
  16. 2026-07-30 21:51 UTCOSV refresh
  17. 2026-07-30 16:26 UTCEPSS rescore
  18. 2026-07-30 01:29 UTCEPSS rescore
  19. 2026-07-28 15:34 UTCEPSS rescore
  20. 2026-07-28 15:34 UTCEPSS rescore
  21. 2026-07-26 14:53 UTCEPSS rescore
  22. 2026-07-25 14:16 UTCEPSS rescore
  23. 2026-07-24 14:16 UTCEPSS rescore
  24. 2026-07-23 14:16 UTCEPSS rescore
  25. 2026-07-23 02:29 UTCEG score recompute
Show 75 more
  1. 2026-07-22 23:15 UTCEG score recompute
  2. 2026-07-22 14:07 UTCEPSS rescore
  3. 2026-07-22 14:07 UTCEPSS rescore
  4. 2026-07-21 15:23 UTCEPSS rescore
  5. 2026-07-20 17:06 UTCEPSS rescore
  6. 2026-07-19 14:30 UTCEPSS rescore
  7. 2026-07-19 14:29 UTCEPSS rescore
  8. 2026-07-19 02:27 UTCEPSS rescore
  9. 2026-07-19 02:27 UTCEPSS rescore
  10. 2026-07-18 10:03 UTCEPSS rescore
  11. 2026-07-18 10:03 UTCEPSS rescore
  12. 2026-07-16 17:01 UTCEPSS rescore
  13. 2026-07-15 16:56 UTCEPSS rescore
  14. 2026-07-15 01:59 UTCEPSS rescore
  15. 2026-07-15 01:59 UTCEPSS rescore
  16. 2026-07-13 22:28 UTCEPSS rescore
  17. 2026-07-13 22:28 UTCEPSS rescore
  18. 2026-07-13 06:38 UTCOSV refresh
  19. 2026-07-13 06:11 UTCEPSS rescore
  20. 2026-07-12 05:45 UTCEPSS rescore
  21. 2026-07-12 05:45 UTCEPSS rescore
  22. 2026-07-11 08:26 UTCEPSS rescore
  23. 2026-07-09 19:08 UTCEPSS rescore
  24. 2026-07-08 15:13 UTCEPSS rescore
  25. 2026-07-07 13:45 UTCEPSS rescore
  26. 2026-07-07 13:44 UTCEPSS rescore
  27. 2026-07-06 16:26 UTCEPSS rescore
  28. 2026-07-06 16:26 UTCEPSS rescore
  29. 2026-07-06 02:22 UTCEPSS rescore
  30. 2026-07-06 02:22 UTCEPSS rescore
  31. 2026-07-05 02:29 UTCEPSS rescore
  32. 2026-07-04 06:29 UTCEPSS rescore
  33. 2026-07-01 15:05 UTCEPSS rescore
  34. 2026-06-30 23:21 UTCEPSS rescore
  35. 2026-06-30 23:21 UTCEPSS rescore
  36. 2026-06-29 14:05 UTCEPSS rescore
  37. 2026-06-28 14:06 UTCEPSS rescore
  38. 2026-06-28 14:06 UTCEPSS rescore
  39. 2026-06-28 04:55 UTCEPSS rescore
  40. 2026-06-27 03:07 UTCEPSS rescore
  41. 2026-06-25 13:48 UTCEPSS rescore
  42. 2026-06-25 13:48 UTCEPSS rescore
  43. 2026-06-24 19:31 UTCOSV refresh
  44. 2026-06-24 14:04 UTCEPSS rescore
  45. 2026-06-24 14:04 UTCEPSS rescore
  46. 2026-06-23 21:31 UTCEPSS rescore
  47. 2026-06-23 21:31 UTCEPSS rescore
  48. 2026-06-22 14:24 UTCEPSS rescore
  49. 2026-06-22 14:24 UTCEPSS rescore
  50. 2026-06-21 14:55 UTCEPSS rescore
  51. 2026-06-21 14:55 UTCEPSS rescore
  52. 2026-06-21 01:58 UTCEPSS rescore
  53. 2026-06-21 01:58 UTCEPSS rescore
  54. 2026-06-19 19:24 UTCEPSS rescore
  55. 2026-06-19 19:24 UTCEPSS rescore
  56. 2026-06-18 17:51 UTCEPSS rescore
  57. 2026-06-17 17:51 UTCEPSS rescore
  58. 2026-06-16 17:51 UTCEPSS rescore
  59. 2026-06-16 17:51 UTCEPSS rescore
  60. 2026-06-15 17:47 UTCEPSS rescore
  61. 2026-06-14 23:16 UTCEPSS rescore
  62. 2026-06-13 22:59 UTCEPSS rescore
  63. 2026-06-13 22:59 UTCEPSS rescore
  64. 2026-06-12 23:11 UTCEPSS rescore
  65. 2026-06-11 13:59 UTCEPSS rescore
  66. 2026-06-10 22:17 UTCEPSS rescore
  67. 2026-06-10 13:21 UTCEPSS rescore
  68. 2026-06-08 14:16 UTCEPSS rescore
  69. 2026-06-08 14:16 UTCEPSS rescore
  70. 2026-06-07 20:46 UTCOSV refresh
  71. 2026-06-07 15:24 UTCEPSS rescore
  72. 2026-06-07 15:24 UTCEPSS rescore
  73. 2026-06-06 13:46 UTCEPSS rescore
  74. 2026-06-06 13:46 UTCEPSS rescore
  75. 2026-06-05 22:46 UTCEPSS rescore

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2023-52491?
CVE-2023-52491 is a high vulnerability published on March 11, 2024. In the Linux kernel, the following vulnerability has been resolved: media: mtk-jpeg: Fix use after free bug due to error path handling in mtkjpegdecdevicerun In mtkjpegprobe, &jpeg->jobtimeoutwork is bound with mtkjpegjobtimeoutwork. In mtkjpegdecdevicerun, if error happens in mtkjpegsetdecdst, it…
When was CVE-2023-52491 disclosed?
CVE-2023-52491 was first published in the National Vulnerability Database on March 11, 2024, with the most recent update on August 5, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-52491 actively exploited?
CVE-2023-52491 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.3% of all scored CVEs.
What is the CVSS score of CVE-2023-52491?
CVE-2023-52491 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2023-52491?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-52491, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2023-52491

Explore →

Is Your Infrastructure Affected by CVE-2023-52491?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs