lists.openwall.net   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  linux-cve-announce  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]
Message-ID: <186242a7-4e63-dccc-0879-1069823f079a@gmail.com>
Date:   Thu, 8 Oct 2020 22:54:17 +0200
From:   Heiner Kallweit <hkallweit1@...il.com>
To:     Eric Dumazet <eric.dumazet@...il.com>,
        Eric Dumazet <edumazet@...gle.com>
Cc:     "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: [Bug 209423] WARN_ON_ONCE() at rtl8169_tso_csum_v2()

On 08.10.2020 21:07, Eric Dumazet wrote:
> 
> 
> On 10/8/20 8:50 PM, Eric Dumazet wrote:
>>
>>
>> OK, it would be nice to know what is the input interface
>>
>> if4 -> look at "ip link | grep 4:"
>>
>> Then identifying the driver that built such a strange packet (32000
>> bytes allocated in skb->head)
>>
>> ethtool -i ifname
>>
> 
> According to https://bugzilla.kernel.org/show_bug.cgi?id=209423
> 
> iif4 is the tun200 interface used by openvpn.
> 
> So this might be a tun bug, or lack of proper SKB_GSO_DODGY validation
> in our stack for buggy/malicious packets.
> 
> 

Following old commit sounds like it might be related:
622e0ca1cd4d ("gro: Fix bogus gso_size on the first fraglist entry")

This code however was removed later in 58025e46ea2d ("net: gro: remove
obsolete code from skb_gro_receive()")

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ