[dpdk-dev] [dpdk-stable] [PATCH 1/2] ip_frag: check fragment length of incoming packet

Thomas Monjalon thomas at monjalon.net
Mon Nov 5 12:37:31 CET 2018


05/11/2018 11:26, Konstantin Ananyev:
> Under some conditions ill-formed fragments might cause
> reassembly code to corrupt mbufs and/or crash.
> Let say the following fragments sequence:
> <ofs=0,len=100, flags=MF>
> <ofs=96,len=100, flags=MF>
> <ofs=200,len=0,flags=MF>
> <ofs=200,len=100,flags=0>
> can trigger the problem.
> To overcome such situation, added check that fragment length
> of incoming value is greater than zero.
> 
> Reported-by: <ryan.e.hall at intel.com>
> Reported-by: <alexander.v.gutkin at intel.com>

Please, could you provide the full names?
Note: it is usually inserted just before your Signed-off.

> Fixes: 601e279df074 ("ip_frag: move fragmentation/reassembly headers into a library")
> Fixes: 4f1a8f633862 ("ip_frag: add IPv6 reassembly")
> Cc: stable at dpdk.org
> 
> Signed-off-by: Konstantin Ananyev <konstantin.ananyev at intel.com>






More information about the dev mailing list