[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190824.142047.32032287178584562.davem@davemloft.net>
Date: Sat, 24 Aug 2019 14:20:47 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: ka-cheong.poon@...cle.com
Cc: netdev@...r.kernel.org, santosh.shilimkar@...cle.com,
rds-devel@....oracle.com
Subject: Re: [PATCH net-next] net/rds: Fix info leak in rds6_inc_info_copy()
From: Ka-Cheong Poon <ka-cheong.poon@...cle.com>
Date: Wed, 21 Aug 2019 20:18:24 -0700
> The rds6_inc_info_copy() function has a couple struct members which
> are leaking stack information. The ->tos field should hold actual
> information and the ->flags field needs to be zeroed out.
>
> Fixes: 3eb450367d08 ("rds: add type of service(tos) infrastructure")
> Fixes: b7ff8b1036f0 ("rds: Extend RDS API for IPv6 support")
> Reported-by: 黄ID蝴蝶 <butterflyhuangxx@...il.com>
> Signed-off-by: Dan Carpenter <dan.carpenter@...cle.com>
> Signed-off-by: Ka-Cheong Poon <ka-cheong.poon@...cle.com>
Why would an info leak bug fix, present in current kernels, be targetted
at 'net-next' instead of 'net'?
Please retarget this at 'net' properly, thank you.
Powered by blists - more mailing lists