CVE-2022-48945

media: vivid: fix compose size exceed boundary

MEDIUM

5.5

CVSS Score

Published: September 23, 2024 at 09:46 AM UTC

Updated: August 5, 2026 at 09:24 AM UTC

1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available

Start Free Sign In

Severity

MEDIUM5.5

Exploit prediction

EPSS 0.2%

SSVC

No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

Linux Kernel · Linux

95%

3.18 ≤ v < 4.14.3033.18 ≤ v < 4.19.2703.18 ≤ v < 4.9.3373.18 ≤ v < 5.10.1633.18 ≤ v < 5.15.863.18 ≤ v < 5.4.2293.18 ≤ v < 6.0.163.18 ≤ v < 6.1.23.18 ≤ v < 6.24.10 ≤ v < 4.14.3034.15 ≤ v < 4.19.2704.20 ≤ v < 5.4.2295.11 ≤ v < 5.15.865.16 ≤ v < 6.0.165.5 ≤ v < 5.10.1636.1 ≤ v < 6.1.23.18ef834f7836ec0502f49f20bbc42f1240577a9c83

Vendor states this is fixed in 2f558c5208b0f70c8140e08ce09fcc84da48e789 (fixed)

Vendor states this is fixed in 54f259906039dbfe46c550011409fa16f72370f6 (fixed)

Vendor states this is fixed in 5edc3604151919da8da0fb092b71d7dce07d848a (fixed)

Vendor states this is fixed in 8c0ee15d9a102c732d0745566d254040085d5663 (fixed)

Vendor states this is fixed in 94a7ad9283464b75b12516c5512541d467cefcf8 (fixed)

Vendor states this is fixed in 9c7fba9503b826f0c061d136f8f0c9f953ed18b9 (fixed)

Vendor states this is fixed in ab54081a2843aefb837812fac5488cc8f1696142 (fixed)

Vendor states this is fixed in ccb5392c4fea0e7d9f7ab35567e839d74cb3998b (fixed)

Vendor states this is fixed in f9d19f3a044ca651b0be52a4bf951ffe74259b9f (fixed)

Vendor states this is fixed in 3.18 (unaffected)

Vendor states this is fixed in 4.14.303 (unaffected)

Vendor states this is fixed in 4.19.270 (unaffected)

Vendor states this is fixed in 4.9.337 (unaffected)

Vendor states this is fixed in 5.10.163 (unaffected)

Vendor states this is fixed in 5.15.86 (unaffected)

Vendor states this is fixed in 5.4.229 (unaffected)

Vendor states this is fixed in 6.0.16 (unaffected)

Vendor states this is fixed in 6.1.2 (unaffected)

Vendor states this is fixed in 6.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

Patch and advisory references