lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 10 Oct 2022 14:19:36 +0200
From:   Nicolas Dichtel <>
To:     Eyal Birger <>
Subject: Re: [PATCH ipsec,v2] xfrm: fix "disable_policy" on ipv4 early demux

Le 10/10/2022 à 12:29, Eyal Birger a écrit :
> Hi Nicolas,
> On Mon, Oct 10, 2022 at 11:28 AM Nicolas Dichtel
> <> wrote:
>> Le 09/10/2022 à 21:16, Eyal Birger a écrit :
>>> The commit in the "Fixes" tag tried to avoid a case where policy check
>>> is ignored due to dst caching in next hops.
>>> However, when the traffic is locally consumed, the dst may be cached
>>> in a local TCP or UDP socket as part of early demux. In this case the
>>> "disable_policy" flag is not checked as ip_route_input_noref() was only
>>> called before caching, and thus, packets after the initial packet in a
>>> flow will be dropped if not matching policies.
>>> Fix by checking the "disable_policy" flag also when a valid dst is
>>> already available.
>>> Link:
>>> Reported-by: Monil Patel <>
>>> Fixes: e6175a2ed1f1 ("xfrm: fix "disable_policy" flag use when arriving from different devices")
>>> Signed-off-by: Eyal Birger <>
>> Is there the same problem with ipv6?
> The issue is specific to IPv4 as the original fix was only relevant
> to IPv4.
> I also tested a similar scenario using IPv6 addresses and did not see
> a problem.
Thanks. Is it possible to write a selftest with this scenario?


Powered by blists - more mailing lists