From: Colin King <hidden> Date: 2017-09-05 18:15:55
From: Colin Ian King <redacted>
The u8 char array ret is not being initialized and elements outside
the range start to end contain just garbage values from the stack.
This results in a later scan of the array to read potentially
uninitialized values. Fix this by initializing the array to zero.
This seems to have been an issue since the very first commit.
Detected by CoverityScan CID#139652 ("Uninitialized scalar variable")
Signed-off-by: Colin Ian King <redacted>
---
drivers/net/wireless/broadcom/b43/phy_g.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Michael Büsch <m@bues.ch> Date: 2017-09-05 20:50:49
On Tue, 5 Sep 2017 19:15:50 +0100
Colin King [off-list ref] wrote:
quoted hunk
From: Colin Ian King <redacted>
The u8 char array ret is not being initialized and elements outside
the range start to end contain just garbage values from the stack.
This results in a later scan of the array to read potentially
uninitialized values. Fix this by initializing the array to zero.
This seems to have been an issue since the very first commit.
Detected by CoverityScan CID#139652 ("Uninitialized scalar variable")
Signed-off-by: Colin Ian King <redacted>
---
drivers/net/wireless/broadcom/b43/phy_g.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
From: Kalle Valo <hidden> Date: 2017-09-20 12:41:27
Colin Ian King [off-list ref] wrote:
From: Colin Ian King <redacted>
The u8 char array ret is not being initialized and elements outside
the range start to end contain just garbage values from the stack.
This results in a later scan of the array to read potentially
uninitialized values. Fix this by initializing the array to zero.
This seems to have been an issue since the very first commit.
Detected by CoverityScan CID#139652 ("Uninitialized scalar variable")
Signed-off-by: Colin Ian King <redacted>
Reviewed-by: Michael Buesch <m@bues.ch>