From: Greg KH <greg@kroah.com>
To: Mauro Carvalho Chehab <mchehab@s-opensource.com>
Cc: stable@vger.kernel.org
Subject: Re: Important regression fix patch
Date: Sat, 14 Apr 2018 16:37:35 +0200 [thread overview]
Message-ID: <20180414143735.GB31434@kroah.com> (raw)
In-Reply-To: <20180413054831.39698e8a@vento.lan>
On Fri, Apr 13, 2018 at 05:48:31AM -0300, Mauro Carvalho Chehab wrote:
> Hi Greg,
>
> There are two important v4l2-core fixes on the patches merged this week by
> Linux.
>
> 1) media: v4l2-core: fix size of devnode_nums[] bitarray
>
> This patch correct a regression against Kernel 4.16. It affects notebooks
> with advanced Synaptics mice (and similar touch devices). On those devices,
> the pad produces an image with is handled via V4L2. Without this patch,
> the input driver OOPSes at probing time:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=a95845ba184b854106972f5d8f50354c2d272c06
>
> 2) v4l2-compat-ioctl32: don't oops on overlay
>
> This patch complements the security fix we've made at the V4L2 core
> compat32 logic. It fixes an illegal use of an __user pointer without
> first convert into a Kernel pointer with get_user(). It wasn't detect
> before, as it uses an obscure streaming mode of V4L2 (overlay mode):
>
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=85ea29f19eab56ec16ec6b92bc67305998706afa
>
> This one should go all the way down to stable Kernels. Here, I was able
> to reproduce the bug with both upstream Kernel and Kernel 3.18. The
> patch applied without any conflicts on both.
>
> Could you please add both on your next set of -stable releases?
Both now queued up, thanks,
greg k-h
prev parent reply other threads:[~2018-04-14 14:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 8:48 Important regression fix patch Mauro Carvalho Chehab
2018-04-14 14:37 ` 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=20180414143735.GB31434@kroah.com \
--to=greg@kroah.com \
--cc=mchehab@s-opensource.com \
--cc=stable@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 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.