From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-58002: media: uvcvideo: Remove dangling pointers
Date: Wed, 26 Feb 2025 18:10:56 -0800 [thread overview]
Message-ID: <2025022654-CVE-2024-58002-6f93@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
media: uvcvideo: Remove dangling pointers
When an async control is written, we copy a pointer to the file handle
that started the operation. That pointer will be used when the device is
done. Which could be anytime in the future.
If the user closes that file descriptor, its structure will be freed,
and there will be one dangling pointer per pending async control, that
the driver will try to use.
Clean all the dangling pointers during release().
To avoid adding a performance penalty in the most common case (no async
operation), a counter has been introduced with some logic to make sure
that it is properly handled.
The Linux kernel CVE team has assigned CVE-2024-58002 to this issue.
Affected and fixed versions
===========================
Issue introduced in 4.19 with commit e5225c820c057537dc780244760e2e24c7d27366 and fixed in 6.12.14 with commit 438bda062b2c40ddd7df23b932e29ffe0a448cac
Issue introduced in 4.19 with commit e5225c820c057537dc780244760e2e24c7d27366 and fixed in 6.13.3 with commit 9edc7d25f7e49c33a1ce7a5ffadea2222065516c
Issue introduced in 4.19 with commit e5225c820c057537dc780244760e2e24c7d27366 and fixed in 6.14-rc1 with commit 221cd51efe4565501a3dbf04cc011b537dcce7fb
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-58002
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/usb/uvc/uvc_ctrl.c
drivers/media/usb/uvc/uvc_v4l2.c
drivers/media/usb/uvc/uvcvideo.h
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/438bda062b2c40ddd7df23b932e29ffe0a448cac
https://git.kernel.org/stable/c/9edc7d25f7e49c33a1ce7a5ffadea2222065516c
https://git.kernel.org/stable/c/221cd51efe4565501a3dbf04cc011b537dcce7fb
reply other threads:[~2025-02-27 2:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2025022654-CVE-2024-58002-6f93@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=cve@kernel.org \
--cc=linux-cve-announce@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.