Re: Bluetooth: Prevent stack info leak from the EFS element.

2018-01-04 Thread gre...@linuxfoundation.org
On Tue, Jan 02, 2018 at 12:26:15PM -0800, Guenter Roeck wrote: > On Fri, Dec 08, 2017 at 03:14:47PM +0100, gre...@linuxfoundation.org wrote: > > From: Ben Seri > > > > In the function l2cap_parse_conf_rsp and in the function > > l2cap_parse_conf_req the following variable is declared without > >

Re: Bluetooth: Prevent stack info leak from the EFS element.

2018-01-02 Thread Guenter Roeck
On Fri, Dec 08, 2017 at 03:14:47PM +0100, gre...@linuxfoundation.org wrote: > From: Ben Seri > > In the function l2cap_parse_conf_rsp and in the function > l2cap_parse_conf_req the following variable is declared without > initialization: > > struct l2cap_conf_efs efs; > > In addition, when pars

[PATCH RESEND] Bluetooth: Prevent stack info leak from the EFS element.

2017-12-18 Thread Greg Kroah-Hartman
From: Ben Seri In the function l2cap_parse_conf_rsp and in the function l2cap_parse_conf_req the following variable is declared without initialization: struct l2cap_conf_efs efs; In addition, when parsing input configuration parameters in both of these functions, the switch case for handling EF

[PATCH] Bluetooth: Prevent stack info leak from the EFS element.

2017-12-08 Thread Greg Kroah-Hartman
From: Ben Seri In the function l2cap_parse_conf_rsp and in the function l2cap_parse_conf_req the following variable is declared without initialization: struct l2cap_conf_efs efs; In addition, when parsing input configuration parameters in both of these functions, the switch case for handling EF