net: irda: using kzalloc() instead of kmalloc() to avoid strncpy() issue.
'discovery->data.info' length is 22, NICKNAME_MAX_LEN is 21, so the strncpy() will always left the last byte of 'discovery->data.info' uninitialized. When 'text' length is longer than 21 (NICKNAME_MAX_LEN), if still left the last byte of 'discovery->data.info' uninitialized, the next strlen() will cause issue. Also 'discovery->data' is 'struct irda_device_info' which defined in "include/uapi/...", it may copy to user mode, so need whole initialized. All together, need use kzalloc() instead of kmalloc() to initialize all members firstly. Signed-off-by: Chen Gang <gang.chen@asianux.com> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
6b21e1b77d
commit
ff0102ee10
|
@ -544,7 +544,7 @@ static void irlap_recv_discovery_xid_cmd(struct irlap_cb *self,
|
|||
/*
|
||||
* We now have some discovery info to deliver!
|
||||
*/
|
||||
discovery = kmalloc(sizeof(discovery_t), GFP_ATOMIC);
|
||||
discovery = kzalloc(sizeof(discovery_t), GFP_ATOMIC);
|
||||
if (!discovery) {
|
||||
IRDA_WARNING("%s: unable to malloc!\n", __func__);
|
||||
return;
|
||||
|
|
Loading…
Reference in New Issue