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 3.14-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-3.14 subdirectory.
If you, or anyone else, feels it should not be added to the stable tree,
please let <[email protected]> know about it.
>From d7b76c91f471413de9ded837bddeca2164786571 Mon Sep 17 00:00:00 2001
From: Mauro Carvalho Chehab <[email protected]>
Date: Tue, 28 Apr 2015 19:02:19 -0300
Subject: [media] af9013: Don't accept invalid bandwidth
From: Mauro Carvalho Chehab <[email protected]>
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 <[email protected]>
Signed-off-by: Greg Kroah-Hartman <[email protected]>
---
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
@@ -606,6 +606,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 [email protected]
are
queue-3.14/cx24116-fix-a-buffer-overflow-when-checking-userspace-params.patch
queue-3.14/saa7164-fix-querycap-warning.patch
queue-3.14/s5h1420-fix-a-buffer-overflow-when-checking-userspace-params.patch
queue-3.14/cx24117-fix-a-buffer-overflow-when-checking-userspace-params.patch
queue-3.14/af9013-don-t-accept-invalid-bandwidth.patch
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
