From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com>
To: Peter Malone <peter.malone@gmail.com>
Cc: Mathieu Malaterre <malat@debian.org>,
Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] Fixing arbitrary kernel leak in case FBIOGETCMAP_SPARC in sbusfb_ioctl_helper().
Date: Wed, 07 Mar 2018 13:03:54 +0000 [thread overview]
Message-ID: <2367982.TLCx2xJjlb@amdc3058> (raw)
In-Reply-To: <CALGb=fQFwgn6=JLq0_5WkwkTpASCXzO_sGPR0BzT3cuF58nzBg@mail.gmail.com>
On Sunday, February 04, 2018 09:18:03 AM Peter Malone wrote:
> Hi folks,
Hi,
> CVE-2018-6412 has been created for this. Is it possible for you to add
> a note indicating the CVE number when merging the patch?
>
> I received the CVE number after the patch was created and ack'd, which
> is why I didn't include it in the commit message.
I queued the patch (with Mathieu's ACK and CVE number added to the patch
description) for v4.16, thanks.
> On Wed, Jan 31, 2018 at 10:49 AM, Mathieu Malaterre <malat@debian.org> wrote:
> > Hi Peter,
> >
> > On Wed, Jan 31, 2018 at 3:57 PM, Peter Malone <peter.malone@gmail.com> wrote:
> >> Fixing arbitrary kernel leak in case FBIOGETCMAP_SPARC in
> >> sbusfb_ioctl_helper().
> >>
> >> 'index' is defined as an int in sbusfb_ioctl_helper().
> >> We retrieve this from the user:
> >> if (get_user(index, &c->index) ||
> >> __get_user(count, &c->count) ||
> >> __get_user(ured, &c->red) ||
> >> __get_user(ugreen, &c->green) ||
> >> __get_user(ublue, &c->blue))
> >> return -EFAULT;
> >>
> >> and then we use 'index' in the following way:
> >> red = cmap->red[index + i] >> 8;
> >> green = cmap->green[index + i] >> 8;
> >> blue = cmap->blue[index + i] >> 8;
> >>
> >> This is a classic information leak vulnerability. 'index' should be
> >> an unsigned int, given its usage above.
> >>
> >> This patch is straight-forward; it changes 'index' to unsigned int
> >> in two switch-cases: FBIOGETCMAP_SPARC && FBIOPUTCMAP_SPARC.
> >>
> >> Signed-off-by: Peter Malone <peter.malone@gmail.com>
> >> ---
> >
> > much better :)
> >
> >> v2: fixed formatting
> >>
> >> drivers/video/fbdev/sbuslib.c | 4 ++--
> >> 1 file changed, 2 insertions(+), 2 deletions(-)
> >>
> >> diff --git a/drivers/video/fbdev/sbuslib.c b/drivers/video/fbdev/sbuslib.c
> >> index af6fc97f4ba4..a436d44f1b7f 100644
> >> --- a/drivers/video/fbdev/sbuslib.c
> >> +++ b/drivers/video/fbdev/sbuslib.c
> >> @@ -122,7 +122,7 @@ int sbusfb_ioctl_helper(unsigned long cmd, unsigned long arg,
> >> unsigned char __user *ured;
> >> unsigned char __user *ugreen;
> >> unsigned char __user *ublue;
> >> - int index, count, i;
> >> + unsigned int index, count, i;
> >>
> >> if (get_user(index, &c->index) ||
> >> __get_user(count, &c->count) ||
> >> @@ -161,7 +161,7 @@ int sbusfb_ioctl_helper(unsigned long cmd, unsigned long arg,
> >> unsigned char __user *ugreen;
> >> unsigned char __user *ublue;
> >> struct fb_cmap *cmap = &info->cmap;
> >> - int index, count, i;
> >> + unsigned int index, count, i;
> >> u8 red, green, blue;
> >>
> >> if (get_user(index, &c->index) ||
> >> --
> >> 2.14.3
> >>
> >
> > By just looking at the code and commit message:
> >
> > Acked-by: Mathieu Malaterre <malat@debian.org>
Best regards,
--
Bartlomiej Zolnierkiewicz
Samsung R&D Institute Poland
Samsung Electronics
prev parent reply other threads:[~2018-03-07 13:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-30 20:30 [PATCH] Fixing arbitrary kernel leak in case FBIOGETCMAP_SPARC in sbusfb_ioctl_helper() Peter Malone
2018-01-31 8:33 ` Mathieu Malaterre
2018-01-31 14:57 ` [PATCH v2] " Peter Malone
2018-01-31 15:49 ` Mathieu Malaterre
2018-02-04 14:18 ` Peter Malone
2018-03-07 13:03 ` Bartlomiej Zolnierkiewicz [this message]
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=2367982.TLCx2xJjlb@amdc3058 \
--to=b.zolnierkie@samsung.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=malat@debian.org \
--cc=peter.malone@gmail.com \
/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).