[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024092346-CVE-2022-48945-90da@gregkh>
Date: Mon, 23 Sep 2024 11:46:47 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2022-48945: media: vivid: fix compose size exceed boundary
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: vivid: fix compose size exceed boundary
syzkaller found a bug:
BUG: unable to handle page fault for address: ffffc9000a3b1000
#PF: supervisor write access in kernel mode
#PF: error_code(0x0002) - not-present page
PGD 100000067 P4D 100000067 PUD 10015f067 PMD 1121ca067 PTE 0
Oops: 0002 [#1] PREEMPT SMP
CPU: 0 PID: 23489 Comm: vivid-000-vid-c Not tainted 6.1.0-rc1+ #512
Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014
RIP: 0010:memcpy_erms+0x6/0x10
[...]
Call Trace:
<TASK>
? tpg_fill_plane_buffer+0x856/0x15b0
vivid_fillbuff+0x8ac/0x1110
vivid_thread_vid_cap_tick+0x361/0xc90
vivid_thread_vid_cap+0x21a/0x3a0
kthread+0x143/0x180
ret_from_fork+0x1f/0x30
</TASK>
This is because we forget to check boundary after adjust compose->height
int V4L2_SEL_TGT_CROP case. Add v4l2_rect_map_inside() to fix this problem
for this case.
The Linux kernel CVE team has assigned CVE-2022-48945 to this issue.
Affected and fixed versions
===========================
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 4.9.337 with commit 8c0ee15d9a10
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 4.14.303 with commit 5edc36041519
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 4.19.270 with commit 9c7fba9503b8
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 5.4.229 with commit 54f259906039
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 5.10.163 with commit f9d19f3a044c
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 5.15.86 with commit ab54081a2843
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 6.0.16 with commit ccb5392c4fea
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 6.1.2 with commit 2f558c5208b0
Issue introduced in 3.18 with commit ef834f7836ec and fixed in 6.2 with commit 94a7ad928346
Please see https://www.kernel.org for a full list of currently supported
kernel versions by the kernel community.
Unaffected versions might change over time as fixes are backported to
older supported kernel versions. The official CVE entry at
https://cve.org/CVERecord/?id=CVE-2022-48945
will be updated if fixes are backported, please check that for the most
up to date information about this issue.
Affected files
==============
The file(s) affected by this issue are:
drivers/media/test-drivers/vivid/vivid-vid-cap.c
Mitigation
==========
The Linux kernel CVE team recommends that you update to the latest
stable kernel version for this, and many other bugfixes. Individual
changes are never tested alone, but rather are part of a larger kernel
release. Cherry-picking individual commits is not recommended or
supported by the Linux kernel community at all. If however, updating to
the latest release is impossible, the individual changes to resolve this
issue can be found at these commits:
https://git.kernel.org/stable/c/8c0ee15d9a102c732d0745566d254040085d5663
https://git.kernel.org/stable/c/5edc3604151919da8da0fb092b71d7dce07d848a
https://git.kernel.org/stable/c/9c7fba9503b826f0c061d136f8f0c9f953ed18b9
https://git.kernel.org/stable/c/54f259906039dbfe46c550011409fa16f72370f6
https://git.kernel.org/stable/c/f9d19f3a044ca651b0be52a4bf951ffe74259b9f
https://git.kernel.org/stable/c/ab54081a2843aefb837812fac5488cc8f1696142
https://git.kernel.org/stable/c/ccb5392c4fea0e7d9f7ab35567e839d74cb3998b
https://git.kernel.org/stable/c/2f558c5208b0f70c8140e08ce09fcc84da48e789
https://git.kernel.org/stable/c/94a7ad9283464b75b12516c5512541d467cefcf8
Powered by blists - more mailing lists