From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: linux-cve-announce@vger.kernel.org
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Subject: CVE-2024-27008: drm: nv04: Fix out of bounds access
Date: Wed, 1 May 2024 07:31:09 +0200 [thread overview]
Message-ID: <2024050148-CVE-2024-27008-5964@gregkh> (raw)
Description
===========
In the Linux kernel, the following vulnerability has been resolved:
drm: nv04: Fix out of bounds access
When Output Resource (dcb->or) value is assigned in
fabricate_dcb_output(), there may be out of bounds access to
dac_users array in case dcb->or is zero because ffs(dcb->or) is
used as index there.
The 'or' argument of fabricate_dcb_output() must be interpreted as a
number of bit to set, not value.
Utilize macros from 'enum nouveau_or' in calls instead of hardcoding.
Found by Linux Verification Center (linuxtesting.org) with SVACE.
The Linux kernel CVE team has assigned CVE-2024-27008 to this issue.
Affected and fixed versions
===========================
Issue introduced in 2.6.38 with commit 2e5702aff395 and fixed in 5.15.157 with commit df0991da7db8
Issue introduced in 2.6.38 with commit 2e5702aff395 and fixed in 6.1.88 with commit 5fd4b090304e
Issue introduced in 2.6.38 with commit 2e5702aff395 and fixed in 6.6.29 with commit 6690cc2732e2
Issue introduced in 2.6.38 with commit 2e5702aff395 and fixed in 6.8.8 with commit 26212da39ee1
Issue introduced in 2.6.38 with commit 2e5702aff395 and fixed in 6.9-rc5 with commit cf92bb778eda
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-27008
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/nouveau/nouveau_bios.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/df0991da7db846f7fa4ec6740350f743d3b69b04
https://git.kernel.org/stable/c/5fd4b090304e450aa0e7cc9cc2b4873285c6face
https://git.kernel.org/stable/c/6690cc2732e2a8d0eaca44dcbac032a4b0148042
https://git.kernel.org/stable/c/26212da39ee14a52c76a202c6ae5153a84f579a5
https://git.kernel.org/stable/c/cf92bb778eda7830e79452c6917efa8474a30c1e
reply other threads:[~2024-05-01 5:32 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=2024050148-CVE-2024-27008-5964@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).