[<prev] [next>] [day] [month] [year] [list]
Message-ID: <2024111950-CVE-2024-50288-1c5d@gregkh>
Date: Tue, 19 Nov 2024 02:32:43 +0100
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: linux-cve-announce@...r.kernel.org
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Subject: CVE-2024-50288: media: vivid: fix buffer overwrite when using > 32 buffers
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: vivid: fix buffer overwrite when using > 32 buffers
The maximum number of buffers that can be requested was increased to
64 for the video capture queue. But video capture used a must_blank
array that was still sized for 32 (VIDEO_MAX_FRAME). This caused an
out-of-bounds write when using buffer indices >= 32.
Create a new define MAX_VID_CAP_BUFFERS that is used to access the
must_blank array and set max_num_buffers for the video capture queue.
This solves a crash reported by:
https://bugzilla.kernel.org/show_bug.cgi?id=219258
The Linux kernel CVE team has assigned CVE-2024-50288 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit cea70ed416b4 and fixed in 6.11.8 with commit e6bacd8f2178
Issue introduced in 6.8 with commit cea70ed416b4 and fixed in 6.12 with commit 96d856956391
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-2024-50288
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-core.c
drivers/media/test-drivers/vivid/vivid-core.h
drivers/media/test-drivers/vivid/vivid-ctrls.c
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/e6bacd8f2178b22859fe6d9f755f19dfcd9d3862
https://git.kernel.org/stable/c/96d8569563916fe2f8fe17317e20e43f54f9ba4b
Powered by blists - more mailing lists