From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> To: Kees Cook <keescook@chromium.org> Cc: Vlad Tsyrklevich <vlad@tsyrklevich.net>, linux-fbdev@vger.kernel.org, Security Officers <security@kernel.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] Fix stack memory disclosure Date: Thu, 10 Jan 2019 16:10:42 +0100 [thread overview] Message-ID: <c0a93d03-f150-6363-2df7-b2dec8a8638a@samsung.com> (raw) In-Reply-To: <CAGXu5jKiKA79mnTwCxTKsXBBKAvaoaX=CH61pLXdxtWQvUhhuQ@mail.gmail.com> On 01/09/2019 12:41 AM, Kees Cook wrote: > On Sat, Jan 5, 2019 at 11:51 PM Vlad Tsyrklevich <vlad@tsyrklevich.net> wrote: >> >> Using [1] for static analysis I found that the OMAPFB_QUERY_PLANE, >> OMAPFB_GET_COLOR_KEY, OMAPFB_GET_DISPLAY_INFO, and OMAPFB_GET_VRAM_INFO >> cases could all leak uninitialized stack memory--either due to >> uninitialized padding or 'reserved' fields. >> >> Fix them by clearing the shared union used to store copied out data. >> >> [1] https://github.com/vlad902/kernel-uninitialized-memory-checker >> >> Signed-off-by: Vlad Tsyrklevich <vlad@tsyrklevich.net> > > Reviewed-by: Kees Cook <keescook@chromium.org> > Fixes: b39a982ddecf ("OMAP: DSS2: omapfb driver") Thanks. > Since this driver is orphaned (according to MAINTAINERS), I think this > fix should go via Bart's tree. Bart, can you take this? Sure, I will merge it tomorrow (I plan to send fbdev fixes pull request to Linus next week). Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics > -Kees > >> Cc: security@kernel.org >> >> --- >> drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c b/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c >> index 53f93616c..8e23160ec 100644 >> --- a/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c >> +++ b/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c >> @@ -609,6 +609,8 @@ int omapfb_ioctl(struct fb_info *fbi, unsigned int cmd, unsigned long arg) >> >> int r = 0; >> >> + memset(&p, 0, sizeof(p)); >> + >> switch (cmd) { >> case OMAPFB_SYNC_GFX: >> DBG("ioctl SYNC_GFX\n"); >> -- >> 2.17.0
WARNING: multiple messages have this Message-ID (diff)
From: Bartlomiej Zolnierkiewicz <b.zolnierkie@samsung.com> To: Kees Cook <keescook@chromium.org> Cc: Vlad Tsyrklevich <vlad@tsyrklevich.net>, linux-fbdev@vger.kernel.org, Security Officers <security@kernel.org>, LKML <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] Fix stack memory disclosure Date: Thu, 10 Jan 2019 15:10:42 +0000 [thread overview] Message-ID: <c0a93d03-f150-6363-2df7-b2dec8a8638a@samsung.com> (raw) In-Reply-To: <CAGXu5jKiKA79mnTwCxTKsXBBKAvaoaX=CH61pLXdxtWQvUhhuQ@mail.gmail.com> On 01/09/2019 12:41 AM, Kees Cook wrote: > On Sat, Jan 5, 2019 at 11:51 PM Vlad Tsyrklevich <vlad@tsyrklevich.net> wrote: >> >> Using [1] for static analysis I found that the OMAPFB_QUERY_PLANE, >> OMAPFB_GET_COLOR_KEY, OMAPFB_GET_DISPLAY_INFO, and OMAPFB_GET_VRAM_INFO >> cases could all leak uninitialized stack memory--either due to >> uninitialized padding or 'reserved' fields. >> >> Fix them by clearing the shared union used to store copied out data. >> >> [1] https://github.com/vlad902/kernel-uninitialized-memory-checker >> >> Signed-off-by: Vlad Tsyrklevich <vlad@tsyrklevich.net> > > Reviewed-by: Kees Cook <keescook@chromium.org> > Fixes: b39a982ddecf ("OMAP: DSS2: omapfb driver") Thanks. > Since this driver is orphaned (according to MAINTAINERS), I think this > fix should go via Bart's tree. Bart, can you take this? Sure, I will merge it tomorrow (I plan to send fbdev fixes pull request to Linus next week). Best regards, -- Bartlomiej Zolnierkiewicz Samsung R&D Institute Poland Samsung Electronics > -Kees > >> Cc: security@kernel.org >> >> --- >> drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c | 2 ++ >> 1 file changed, 2 insertions(+) >> >> diff --git a/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c b/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c >> index 53f93616c..8e23160ec 100644 >> --- a/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c >> +++ b/drivers/video/fbdev/omap2/omapfb/omapfb-ioctl.c >> @@ -609,6 +609,8 @@ int omapfb_ioctl(struct fb_info *fbi, unsigned int cmd, unsigned long arg) >> >> int r = 0; >> >> + memset(&p, 0, sizeof(p)); >> + >> switch (cmd) { >> case OMAPFB_SYNC_GFX: >> DBG("ioctl SYNC_GFX\n"); >> -- >> 2.17.0
next prev parent reply other threads:[~2019-01-10 15:10 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-01-06 7:54 [PATCH] Fix stack memory disclosure Vlad Tsyrklevich 2019-01-08 23:41 ` Kees Cook 2019-01-08 23:41 ` Kees Cook 2019-01-10 15:10 ` Bartlomiej Zolnierkiewicz [this message] 2019-01-10 15:10 ` Bartlomiej Zolnierkiewicz 2019-01-11 12:45 ` Bartlomiej Zolnierkiewicz 2019-01-11 12:45 ` Bartlomiej Zolnierkiewicz
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=c0a93d03-f150-6363-2df7-b2dec8a8638a@samsung.com \ --to=b.zolnierkie@samsung.com \ --cc=keescook@chromium.org \ --cc=linux-fbdev@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=security@kernel.org \ --cc=vlad@tsyrklevich.net \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.