{
  "cveId": "CVE-2023-52491",
  "url": "https://patchblox.com/security/cve/CVE-2023-52491",
  "summary": "CVE-2023-52491 is fixed in linux on 1 platform, first by DEBIAN-CVE-2023-52491, released March 11, 2024. It is not reported as exploited. Patch Radar priority: High.",
  "title": "linux: In the Linux kernel, the following vulnerability has been resolved:  media: mtk-jpeg: Fix use after free bug due to e...",
  "description": "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, \u0026jpeg-\u003Ejob_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\t    |                     |mtk_jpeg_job_timeout_work mtk_jpeg_remove     |   v4l2_m2m_release  |     kfree(m2m_dev); |                     |                     | v4l2_m2m_get_curr_priv                     |   m2m_dev-\u003Ecurr_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.",
  "published": "2024-03-11T18:15:16Z",
  "severity": "high",
  "cvss": 7.8,
  "cvssVector": "CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H",
  "epss": 0.00278,
  "epssPercentile": 0.20358,
  "priority": "High",
  "priorityTier": 3,
  "exploited": false,
  "vendorExploited": false,
  "disclosed": false,
  "fixes": [
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 12.15 (bookworm)",
      "fixedVersion": "6.1.76-1",
      "fix": "DEBIAN-CVE-2023-52491",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52491",
      "released": "2024-03-11T18:15:16Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 13.5 (trixie)",
      "fixedVersion": "6.6.15-1",
      "fix": "DEBIAN-CVE-2023-52491",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52491",
      "released": "2024-03-11T18:15:16Z"
    },
    {
      "platform": "linux",
      "product": "linux",
      "release": "Debian 14",
      "fixedVersion": "6.6.15-1",
      "fix": "DEBIAN-CVE-2023-52491",
      "url": "https://patchblox.com/security/fix/linux/debian-cve-2023-52491",
      "released": "2024-03-11T18:15:16Z"
    }
  ],
  "noFixYet": [],
  "dataAsOf": "2026-11-08T19:12:23Z",
  "attribution": {
    "text": "Data: Patchblox Patch Radar",
    "url": "https://patchblox.com/security/patch-radar",
    "terms": "https://patchblox.com/security/patch-radar/use-the-data"
  }
}