From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: Laurent Pinchart <laurent.pinchart@skynet.be>,
linux-media@vger.kernel.org, nm127@freemail.hu
Subject: Re: [RFC,PATCH] VIDIOC_G_EXT_CTRLS does not handle NULL pointer correctly
Date: Wed, 10 Jun 2009 10:52:28 -0300 [thread overview]
Message-ID: <20090610105228.3ca409ba@pedra.chehab.org> (raw)
In-Reply-To: <20090525111634.0f9593be@pedra.chehab.org>
Em Mon, 25 May 2009 11:16:34 -0300
Mauro Carvalho Chehab <mchehab@infradead.org> escreveu:
> Em Mon, 25 May 2009 13:17:02 +0200
> Laurent Pinchart <laurent.pinchart@skynet.be> escreveu:
>
> > Hi everybody,
> >
> > Márton Németh found an integer overflow bug in the extended control ioctl
> > handling code. This affects both video_usercopy and video_ioctl2. See
> > http://bugzilla.kernel.org/show_bug.cgi?id=13357 for a detailed description of
> > the problem.
> >
>
> > Restricting v4l2_ext_controls::count to values smaller than KMALLOC_MAX_SIZE /
> > sizeof(struct v4l2_ext_control) should be enough, but we might want to
> > restrict the value even further. I'd like opinions on this.
>
> Seems fine to my eyes, but being so close to kmalloc size doesn't seem to be a
> good idea. It seems better to choose an arbitrary size big enough to handle all current needs.
I'll apply the current version, but I still think we should restrict it to a lower value.
Cheers,
Mauro
next prev parent reply other threads:[~2009-06-10 13:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-25 11:17 [RFC,PATCH] VIDIOC_G_EXT_CTRLS does not handle NULL pointer correctly Laurent Pinchart
2009-05-25 14:16 ` Mauro Carvalho Chehab
2009-06-10 13:52 ` Mauro Carvalho Chehab [this message]
2009-06-10 13:53 ` Mauro Carvalho Chehab
2009-06-10 15:49 ` Németh Márton
2009-06-10 21:58 ` Laurent Pinchart
2009-12-10 11:14 ` Laurent Pinchart
2009-12-10 17:22 ` Németh Márton
2009-05-25 19:22 ` Trent Piepho
2009-05-27 15:27 ` Laurent Pinchart
2009-05-28 6:44 ` Németh Márton
-- strict thread matches above, loose matches on Subject: below --
2009-05-27 15:26 [RFC, PATCH] " Hans Verkuil
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=20090610105228.3ca409ba@pedra.chehab.org \
--to=mchehab@infradead.org \
--cc=laurent.pinchart@skynet.be \
--cc=linux-media@vger.kernel.org \
--cc=nm127@freemail.hu \
/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