All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Cc: tglx@linutronix.de, crope@iki.fi, linux-media@vger.kernel.org,
	rfontana@redhat.com, erik.andren@gmail.com, hverkuil@xs4all.nl,
	brijohn@gmail.com, lcostantino@gmail.com, suweifeng1@huawei.com,
	Mingfangsen <mingfangsen@huawei.com>,
	guiyao@huawei.com
Subject: Re: [PATCH] media: usb/cpia2: fix start_offset+size Integer Overflow in, cpia2_remap_buffer
Date: Thu, 12 Dec 2019 11:01:53 +0100	[thread overview]
Message-ID: <20191212100153.GA1468094@kroah.com> (raw)
In-Reply-To: <bba0386d-fb55-ecde-6bd9-8a75ea29d5fb@huawei.com>

On Thu, Dec 12, 2019 at 05:40:54PM +0800, Zhiqiang Liu wrote:
> 
> 
> On 2019/12/12 15:47, Greg KH wrote:
> > On Thu, Dec 12, 2019 at 09:48:44AM +0800, Zhiqiang Liu wrote:
> >> Omer Shalev have given a example which can trigger the CVE.
> >> Example link: https://deshal3v.github.io/blog/kernel-research/mmap_exploitation
> > 
> > That "example" was run on a kernel without the above mentioned commit to
> > fix all of this.
> > 
> > Have you tried this on the latest kernel release and succeeded?
> > 
> > thanks,
> > 
> > greg k-h
> > 
> 
> Thanks for patiently answering my question.
> Actually, I have missed the Omer's commit.

As pennance, you can go revoke that CVE so this doesn't come up again in
a few months from someone else :)

thanks,

greg k-h

      reply	other threads:[~2019-12-12 10:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-11  2:47 [PATCH] media: usb/cpia2: fix start_offset+size Integer Overflow in, cpia2_remap_buffer Zhiqiang Liu
2019-12-11  7:57 ` Greg KH
2019-12-12  1:48   ` Zhiqiang Liu
2019-12-12  7:47     ` Greg KH
2019-12-12  9:40       ` Zhiqiang Liu
2019-12-12 10:01         ` Greg KH [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=20191212100153.GA1468094@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=brijohn@gmail.com \
    --cc=crope@iki.fi \
    --cc=erik.andren@gmail.com \
    --cc=guiyao@huawei.com \
    --cc=hverkuil@xs4all.nl \
    --cc=lcostantino@gmail.com \
    --cc=linux-media@vger.kernel.org \
    --cc=liuzhiqiang26@huawei.com \
    --cc=mingfangsen@huawei.com \
    --cc=rfontana@redhat.com \
    --cc=suweifeng1@huawei.com \
    --cc=tglx@linutronix.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 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.