Bug#960702: [PATCH net] mlx4: Fix information leak on failure to read module EEPROM

2020-05-18 Thread Ben Hutchings
On Mon, 2020-05-18 at 16:47 +, Saeed Mahameed wrote: > On Sun, 2020-05-17 at 18:20 +0100, Ben Hutchings wrote: > > mlx4_en_get_module_eeprom() returns 0 even if it fails. This results > > in copying an uninitialised (or partly initialised) buffer back to > > user-space. [...] > I am not sure

Bug#960702: [PATCH net] mlx4: Fix information leak on failure to read module EEPROM

2020-05-18 Thread Saeed Mahameed
On Sun, 2020-05-17 at 18:20 +0100, Ben Hutchings wrote: > mlx4_en_get_module_eeprom() returns 0 even if it fails. This results > in copying an uninitialised (or partly initialised) buffer back to > user-space. > > Change it so that: > > * In the special case that the DOM turns out not to be

Bug#960702: [PATCH net] mlx4: Fix information leak on failure to read module EEPROM

2020-05-17 Thread Ben Hutchings
mlx4_en_get_module_eeprom() returns 0 even if it fails. This results in copying an uninitialised (or partly initialised) buffer back to user-space. Change it so that: * In the special case that the DOM turns out not to be readable, the remaining part of the buffer is cleared. This should