From: Yuki Machida <machida.yuki@jp•fujitsu.com>
To: Greg KH <gregkh@linuxfoundation•org>
Cc: netdev@vger•kernel.org, "Salva Peiró" <speirofr@gmail•com>,
"Hans Verkuil" <hans.verkuil@cisco•com>,
"Mauro Carvalho Chehab" <mchehab@osg•samsung.com>
Subject: Re: [PATCH 4.1] [media] media/vivid-osd: fix info leak in ioctl
Date: Wed, 27 Jan 2016 16:59:57 +0900 [thread overview]
Message-ID: <56A878FD.7070905@jp.fujitsu.com> (raw)
In-Reply-To: <20160125171844.GA27264@kroah.com>
Hi Greg,
On 2016年01月26日 02:18, Greg KH wrote:
> On Mon, Jan 25, 2016 at 07:42:18PM +0900, Yuki Machida wrote:
>> commit eda98796aff0d9bf41094b06811f5def3b4c333c upstream.
>>
>> The vivid_fb_ioctl() code fails to initialize the 16 _reserved bytes of
>> struct fb_vblank after the ->hcount member. Add an explicit
>> memset(0) before filling the structure to avoid the info leak.
>>
>> This fixes CVE-2015-7884.
>>
>> Signed-off-by: Salva Peiró <speirofr@gmail•com>
>> Signed-off-by: Hans Verkuil <hans.verkuil@cisco•com>
>> Signed-off-by: Mauro Carvalho Chehab <mchehab@osg•samsung.com>
>> Signed-off-by: Yuki Machida <machida.yuki@jp•fujitsu.com>
>> ---
>> drivers/media/platform/vivid/vivid-osd.c | 1 +
>> 1 file changed, 1 insertion(+)
>
> <formletter>
>
> This is not the correct way to submit patches for inclusion in the
> stable kernel tree. Please read Documentation/stable_kernel_rules.txt
> for how to do this properly.
Thank you for your advice.
I will check stable_kernel_rules.txt again.
> </formletter>
>
next prev parent reply other threads:[~2016-01-27 8:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 10:42 [PATCH 4.1] [media] media/vivid-osd: fix info leak in ioctl Yuki Machida
2016-01-25 17:18 ` Greg KH
2016-01-27 7:59 ` Yuki Machida [this message]
2016-01-25 23:44 ` Yuki Machida
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=56A878FD.7070905@jp.fujitsu.com \
--to=machida.yuki@jp$(echo .)fujitsu.com \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=hans.verkuil@cisco$(echo .)com \
--cc=mchehab@osg$(echo .)samsung.com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=speirofr@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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