From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-49984: drm/v3d: Prevent out of bounds access in performance query extensions
Date: Mon, 21 Oct 2024 20:03:12 +0200 [thread overview]
Message-ID: <2024102136-CVE-2024-49984-e47f@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm/v3d: Prevent out of bounds access in performance query extensions
Check that the number of perfmons userspace is passing in the copy and
reset extensions is not greater than the internal kernel storage where
the ids will be copied into.
The Linux kernel CVE team has assigned CVE-2024-49984 to this issue.
Affected and fixed versions
===========================
Issue introduced in 6.8 with commit bae7cb5d6800 and fixed in 6.10.4 with commit 73ad583bd493
Issue introduced in 6.8 with commit bae7cb5d6800 and fixed in 6.10.14 with commit 3e50d72abe50
Issue introduced in 6.8 with commit bae7cb5d6800 and fixed in 6.11.3 with commit d9536f16be39
Issue introduced in 6.8 with commit bae7cb5d6800 and fixed in 6.12-rc1 with commit f32b5128d2c4
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-49984
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/gpu/drm/v3d/v3d_submit.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/73ad583bd4938bf37d2709fc36901eb6f22f2722
https://git.kernel.org/stable/c/3e50d72abe50204c7b19784a66e86da29dde32c2
https://git.kernel.org/stable/c/d9536f16be3970c170571efa707c13cd089c774e
https://git.kernel.org/stable/c/f32b5128d2c440368b5bf3a7a356823e235caabb
reply other threads:[~2024-10-21 18:07 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=2024102136-CVE-2024-49984-e47f@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.