netdev - Re: [PATCH] fragment: Improved handling of incorrect IP fragments

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]

Date:   Fri, 03 Jan 2020 00:44:30 +0000
From:   Ttttabcd <ttttabcd@...tonmail.com>
To:     Stephen Hemminger <stephen@...workplumber.org>
Cc:     Netdev <netdev@...r.kernel.org>,
        David Miller <davem@...emloft.net>,
        "kuznet@....inr.ac.ru" <kuznet@....inr.ac.ru>,
        "yoshfuji@...ux-ipv6.org" <yoshfuji@...ux-ipv6.org>
Subject: Re: [PATCH] fragment: Improved handling of incorrect IP fragments

> You can not safely drop this check.
> With recursive fragmentation it is possible that the initial payload ends
> up exceeding the maximum packet length.

Can you give an example? What is "recursive fragmentation"?

In my previous tests, all fragment packets with a payload length exceeding 65535 will be in the ip6_frag_queue

if ((unsigned int) end> IPV6_MAXPLEN)

Was discarded.