From: Danilo Krummrich <dakr@redhat.com>
To: Mikhail Kobuk <m.kobuk@ispras.ru>,
Karol Herbst <kherbst@redhat.com>, Lyude Paul <lyude@redhat.com>
Cc: David Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>,
Francisco Jerez <currojerez@riseup.net>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org,
Fedor Pchelkin <pchelkin@ispras.ru>,
Alexey Khoroshilov <khoroshilov@ispras.ru>
Subject: Re: [PATCH] drm: nv04: Add check to avoid out of bounds access
Date: Fri, 5 Apr 2024 17:53:26 +0200 [thread overview]
Message-ID: <c3253f8a-e654-4016-b0c6-d92703107c48@redhat.com> (raw)
In-Reply-To: <20240331064552.6112-1-m.kobuk@ispras.ru>
On 3/31/24 08:45, Mikhail Kobuk wrote:
> Output Resource (dcb->or) value is not guaranteed to be non-zero (i.e.
> in drivers/gpu/drm/nouveau/nouveau_bios.c, in 'fabricate_dcb_encoder_table()'
> 'dcb->or' is assigned value '0' in call to 'fabricate_dcb_output()').
I don't really know much about the semantics of this code.
Looking at fabricate_dcb_output() though I wonder if the intention was to assign
BIT(or) to entry->or.
@Lyude, can you help here?
Otherwise, for parsing the DCB entries, it seems that the bound checks are
happening in olddcb_outp_foreach() [1].
[1] https://elixir.bootlin.com/linux/latest/source/drivers/gpu/drm/nouveau/nouveau_bios.c#L1331
>
> Add check to validate 'dcb->or' before it's used.
>
> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
> Fixes: 2e5702aff395 ("drm/nouveau: fabricate DCB encoder table for iMac G4")
> Signed-off-by: Mikhail Kobuk <m.kobuk@ispras.ru>
> ---
> drivers/gpu/drm/nouveau/dispnv04/dac.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/nouveau/dispnv04/dac.c b/drivers/gpu/drm/nouveau/dispnv04/dac.c
> index d6b8e0cce2ac..0c8d4fc95ff3 100644
> --- a/drivers/gpu/drm/nouveau/dispnv04/dac.c
> +++ b/drivers/gpu/drm/nouveau/dispnv04/dac.c
> @@ -428,7 +428,7 @@ void nv04_dac_update_dacclk(struct drm_encoder *encoder, bool enable)
> struct drm_device *dev = encoder->dev;
> struct dcb_output *dcb = nouveau_encoder(encoder)->dcb;
>
> - if (nv_gf4_disp_arch(dev)) {
> + if (nv_gf4_disp_arch(dev) && ffs(dcb->or)) {
> uint32_t *dac_users = &nv04_display(dev)->dac_users[ffs(dcb->or) - 1];
> int dacclk_off = NV_PRAMDAC_DACCLK + nv04_dac_output_offset(encoder);
> uint32_t dacclk = NVReadRAMDAC(dev, 0, dacclk_off);
> @@ -453,7 +453,7 @@ bool nv04_dac_in_use(struct drm_encoder *encoder)
> struct drm_device *dev = encoder->dev;
> struct dcb_output *dcb = nouveau_encoder(encoder)->dcb;
>
> - return nv_gf4_disp_arch(encoder->dev) &&
> + return nv_gf4_disp_arch(encoder->dev) && ffs(dcb->or) &&
> (nv04_display(dev)->dac_users[ffs(dcb->or) - 1] & ~(1 << dcb->index));
> }
>
next prev parent reply other threads:[~2024-04-05 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-31 6:45 Mikhail Kobuk
2024-04-05 15:53 ` Danilo Krummrich [this message]
2024-04-05 20:05 ` Lyude Paul
2024-04-08 13:23 ` Danilo Krummrich
2024-04-10 15:39 ` Mikhail Kobuk
2024-04-10 16:24 ` Danilo Krummrich
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=c3253f8a-e654-4016-b0c6-d92703107c48@redhat.com \
--to=dakr@redhat.com \
--cc=airlied@gmail.com \
--cc=currojerez@riseup.net \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=kherbst@redhat.com \
--cc=khoroshilov@ispras.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lvc-project@linuxtesting.org \
--cc=lyude@redhat.com \
--cc=m.kobuk@ispras.ru \
--cc=nouveau@lists.freedesktop.org \
--cc=pchelkin@ispras.ru \
/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
all inboxes | Powered by JetHome®