From: Kees Cook <keescook@chromium.org>
To: Jiawei Gu <Jiawei.Gu@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>
Cc: "StDenis, Tom" <Tom.StDenis@amd.com>,
"Deucher, Alexander" <Alexander.Deucher@amd.com>,
"Christian König" <ckoenig.leichtzumerken@gmail.com>,
"Gu, JiaWei (Will)" <JiaWei.Gu@amd.com>,
"amd-gfx@lists.freedesktop.org" <amd-gfx@lists.freedesktop.org>,
"Nieto, David M" <David.Nieto@amd.com>,
linux-next@vger.kernel.org
Subject: Re: [PATCH] drm/amdgpu: Add vbios info ioctl interface
Date: Fri, 7 May 2021 21:28:23 -0700 [thread overview]
Message-ID: <202105072117.1480D10A@keescook> (raw)
In-Reply-To: <20210422023448.24689-1-Jiawei.Gu@amd.com>
Hi!
This patch needs some fixing.
On Thu, Apr 22, 2021 at 10:34:48AM +0800, Jiawei Gu wrote:
> + case AMDGPU_INFO_VBIOS_INFO: {
> + struct drm_amdgpu_info_vbios vbios_info = {};
> + struct atom_context *atom_context;
> +
> + atom_context = adev->mode_info.atom_context;
> + memcpy(vbios_info.name, atom_context->name, sizeof(atom_context->name));
> + vbios_info.dbdf = PCI_DEVID(adev->pdev->bus->number, adev->pdev->devfn);
> + memcpy(vbios_info.vbios_pn, atom_context->vbios_pn, sizeof(atom_context->vbios_pn));
> + vbios_info.version = atom_context->version;
> + memcpy(vbios_info.date, atom_context->date, sizeof(atom_context->date));
> + memcpy(vbios_info.serial, adev->serial, sizeof(adev->serial));
This writes beyond the end of vbios_info.serial.
> + vbios_info.dev_id = adev->pdev->device;
> + vbios_info.rev_id = adev->pdev->revision;
> + vbios_info.sub_dev_id = atom_context->sub_dev_id;
> + vbios_info.sub_ved_id = atom_context->sub_ved_id;
Though it gets "repaired" by these writes.
> +
> + return copy_to_user(out, &vbios_info,
> + min((size_t)size, sizeof(vbios_info))) ? -EFAULT : 0;
> + }
sizeof(adev->serial) != sizeof(vbios_info.serial)
adev is struct amdgpu_device:
struct amdgpu_device {
...
char serial[20];
> +struct drm_amdgpu_info_vbios {
> [...]
> + __u8 serial[16];
> + __u32 dev_id;
> + __u32 rev_id;
> + __u32 sub_dev_id;
> + __u32 sub_ved_id;
> +};
Is there a truncation issue (20 vs 16) and is this intended to be a
NUL-terminated string?
--
Kees Cook
next parent reply other threads:[~2021-05-08 4:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210422023448.24689-1-Jiawei.Gu@amd.com>
2021-05-08 4:28 ` Kees Cook [this message]
2021-05-08 6:01 ` [PATCH] drm/amdgpu: Add vbios info ioctl interface Gu, JiaWei (Will)
2021-05-08 9:51 ` Kees Cook
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=202105072117.1480D10A@keescook \
--to=keescook@chromium.org \
--cc=Alexander.Deucher@amd.com \
--cc=David.Nieto@amd.com \
--cc=Jiawei.Gu@amd.com \
--cc=Tom.StDenis@amd.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=ckoenig.leichtzumerken@gmail.com \
--cc=linux-next@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