From: coverity-bot <keescook@chromium.org>
To: Ben Skeggs <bskeggs@redhat.com>
Cc: Thomas Zimmermann <tzimmermann@suse.de>,
linux-kernel@vger.kernel.org, Daniel Vetter <daniel@ffwll.ch>,
Lyude Paul <lyude@redhat.com>, Karol Herbst <kherbst@redhat.com>,
David Airlie <airlied@gmail.com>,
dri-devel@lists.freedesktop.org, nouveau@lists.freedesktop.org,
Jani Nikula <jani.nikula@intel.com>,
Dave Airlie <airlied@redhat.com>,
"Gustavo A. R. Silva" <gustavo@embeddedor.com>,
linux-next@vger.kernel.org, linux-hardening@vger.kernel.org
Subject: Coverity: nv50_hdmi_enable(): OVERRUN
Date: Thu, 10 Nov 2022 08:42:57 -0800 [thread overview]
Message-ID: <202211100842.076585A@keescook> (raw)
Hello!
This is an experimental semi-automated report about issues detected by
Coverity from a scan of next-20221110 as part of the linux-next scan project:
https://scan.coverity.com/projects/linux-next-weekly-scan
You're getting this email because you were associated with the identified
lines of code (noted below) that were touched by commits:
Wed Nov 9 08:22:02 2022 +1000
f530bc60a30b ("drm/nouveau/disp: move HDMI config into acquire + infoframe methods")
Coverity reported the following:
*** CID 1527272: (OVERRUN)
drivers/gpu/drm/nouveau/dispnv50/disp.c:801 in nv50_hdmi_enable()
795
796 size = hdmi_infoframe_pack(&infoframe, args.data, 17);
797 } else {
798 size = 0;
799 }
800
vvv CID 1527272: (OVERRUN)
vvv Overrunning struct type nvif_outp_infoframe_v0 of 8 bytes by passing it to a function which accesses it at byte offset 21 using argument "size" (which evaluates to 14).
801 nvif_outp_infoframe(&nv_encoder->outp, NVIF_OUTP_INFOFRAME_V0_AVI, &args.infoframe, size);
802
803 /* Vendor InfoFrame. */
804 if (!drm_hdmi_vendor_infoframe_from_display_mode(&infoframe.vendor.hdmi,
805 &nv_connector->base, mode))
806 size = hdmi_infoframe_pack(&infoframe, args.data, 17);
drivers/gpu/drm/nouveau/dispnv50/disp.c:810 in nv50_hdmi_enable()
804 if (!drm_hdmi_vendor_infoframe_from_display_mode(&infoframe.vendor.hdmi,
805 &nv_connector->base, mode))
806 size = hdmi_infoframe_pack(&infoframe, args.data, 17);
807 else
808 size = 0;
809
vvv CID 1527272: (OVERRUN)
vvv Overrunning struct type nvif_outp_infoframe_v0 of 8 bytes by passing it to a function which accesses it at byte offset 21 using argument "size" (which evaluates to 14).
810 nvif_outp_infoframe(&nv_encoder->outp, NVIF_OUTP_INFOFRAME_V0_VSI, &args.infoframe, size);
811
812 nv50_audio_enable(encoder, nv_crtc, nv_connector, state, mode);
813 }
814
815 /******************************************************************************
If this is a false positive, please let us know so we can mark it as
such, or teach the Coverity rules to be smarter. If not, please make
sure fixes get into linux-next. :) For patches fixing this, please
include these lines (but double-check the "Fixes" first):
Reported-by: coverity-bot <keescook+coverity-bot@chromium.org>
Addresses-Coverity-ID: 1527272 ("OVERRUN")
Fixes: f530bc60a30b ("drm/nouveau/disp: move HDMI config into acquire + infoframe methods")
It looks like this should address &args not &args.infoframe, if the
intention is to include the "data" member.
Thanks for your attention!
--
Coverity-bot
reply other threads:[~2022-11-10 16:43 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=202211100842.076585A@keescook \
--to=keescook@chromium.org \
--cc=airlied@gmail.com \
--cc=airlied@redhat.com \
--cc=bskeggs@redhat.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=gustavo@embeddedor.com \
--cc=jani.nikula@intel.com \
--cc=kherbst@redhat.com \
--cc=linux-hardening@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=lyude@redhat.com \
--cc=nouveau@lists.freedesktop.org \
--cc=tzimmermann@suse.de \
/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