Bug 1221281 (CVE-2023-52491) - VUL-0: CVE-2023-52491: kernel: media: mtk-jpeg: Fix use after free bug due to error path handling in mtk_jpeg_dec_device_run
Summary: VUL-0: CVE-2023-52491: kernel: media: mtk-jpeg: Fix use after free bug due to...
Status: IN_PROGRESS
Alias: CVE-2023-52491
Product: SUSE Security Incidents
Classification: Novell Products
Component: Incidents (show other bugs)
Version: unspecified
Hardware: Other Other
: P3 - Medium : Normal
Target Milestone: ---
Assignee: Security Team bot
QA Contact: Security Team bot
URL: https://smash.suse.de/issue/397132/
Whiteboard: CVSSv3.1:SUSE:CVE-2023-52491:6.2:(AV:...
Keywords:
Depends on:
Blocks:
 
Reported: 2024-03-12 10:05 UTC by SMASH SMASH
Modified: 2024-06-25 18:20 UTC (History)
3 users (show)

See Also:
Found By: Security Response Team
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description SMASH SMASH 2024-03-12 10:05:24 UTC
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.

References:
http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2023-52491
https://git.kernel.org/stable/c/9fec4db7fff54d9b0306a332bab31eac47eeb5f6
https://www.cve.org/CVERecord?id=CVE-2023-52491
https://git.kernel.org/stable/c/1b1036c60a37a30caf6759a90fe5ecd06ec35590
https://git.kernel.org/stable/c/206c857dd17d4d026de85866f1b5f0969f2a109e
https://git.kernel.org/stable/c/43872f44eee6c6781fea1348b38885d8e78face9
https://git.kernel.org/stable/c/6e2f37022f0fc0893da4d85a0500c9d547fffd4c
https://git.kernel.org/stable/c/8254d54d00eb6cdb8367399c7f912eb8d354ecd7
Comment 3 Ivan Ivanov 2024-03-22 09:04:04 UTC
What is CVSS score?
Comment 4 Robert Frohl 2024-03-22 09:20:55 UTC
(In reply to Ivan Ivanov from comment #3)
> What is CVSS score?

updated
Comment 14 Ivan Ivanov 2024-04-12 13:02:55 UTC
Patch have wrong Fixes tag.

Instead:

Fixes: b2f0d2724ba4 ("[media] vcodec: mediatek: Add Mediatek JPEG Decoder Driver")

it should be no older than:

Fixes: 5fb1c2361e56 ("mtk-jpegenc: add jpeg encode worker interface")

$ git describe 5fb1c2361e56
v6.0-rc1-288-g5fb1c2361e56

And this is already fixed and tagged properly in 6.4 based branches.

So nothing to do here. Back to security team.