From: <gregkh@linuxfoundation.org>
To: mchehab@osg.samsung.com, gregkh@linuxfoundation.org
Cc: <stable@vger.kernel.org>, <stable-commits@vger.kernel.org>
Subject: Patch "[media] af9013: Don't accept invalid bandwidth" has been added to the 4.1-stable tree
Date: Wed, 29 Jul 2015 17:25:13 -0700 [thread overview]
Message-ID: <143821591329229@kroah.com> (raw)
This is a note to let you know that I've just added the patch titled
[media] af9013: Don't accept invalid bandwidth
to the 4.1-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
af9013-don-t-accept-invalid-bandwidth.patch
and it can be found in the queue-4.1 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <stable@vger.kernel.org> know about it.
>From d7b76c91f471413de9ded837bddeca2164786571 Mon Sep 17 00:00:00 2001
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Date: Tue, 28 Apr 2015 19:02:19 -0300
Subject: [media] af9013: Don't accept invalid bandwidth
From: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
commit d7b76c91f471413de9ded837bddeca2164786571 upstream.
If userspace sends an invalid bandwidth, it should either return
EINVAL or switch to auto mode.
This driver will go past an array and program the hardware on a
wrong way if this happens.
Signed-off-by: Mauro Carvalho Chehab <mchehab@osg.samsung.com>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
---
drivers/media/dvb-frontends/af9013.c | 4 ++++
1 file changed, 4 insertions(+)
--- a/drivers/media/dvb-frontends/af9013.c
+++ b/drivers/media/dvb-frontends/af9013.c
@@ -605,6 +605,10 @@ static int af9013_set_frontend(struct dv
}
}
+ /* Return an error if can't find bandwidth or the right clock */
+ if (i == ARRAY_SIZE(coeff_lut))
+ return -EINVAL;
+
ret = af9013_wr_regs(state, 0xae00, coeff_lut[i].val,
sizeof(coeff_lut[i].val));
}
Patches currently in stable-queue which might be from mchehab@osg.samsung.com are
queue-4.1/media-fix-regression-in-some-more-dib0700-based-devices.patch
queue-4.1/cx24116-fix-a-buffer-overflow-when-checking-userspace-params.patch
queue-4.1/saa7164-fix-querycap-warning.patch
queue-4.1/vb2-don-t-warn-when-v4l2_buffer.bytesused-is-0-for-multiplanar-buffers.patch
queue-4.1/s5h1420-fix-a-buffer-overflow-when-checking-userspace-params.patch
queue-4.1/rc-core-fix-dib0700-scancode-generation-for-rc5.patch
queue-4.1/cx24117-fix-a-buffer-overflow-when-checking-userspace-params.patch
queue-4.1/af9013-don-t-accept-invalid-bandwidth.patch
queue-4.1/cx18-add-missing-caps-for-the-pcm-video-device.patch
reply other threads:[~2015-07-30 0:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=143821591329229@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=mchehab@osg.samsung.com \
--cc=stable-commits@vger.kernel.org \
--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.