From: Jakub Kicinski <kuba@kernel.org>
To: Tom Herbert <tom@herbertland.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
justin.iurman@uliege.be, willemdebruijn.kernel@gmail.com,
pabeni@redhat.com
Subject: Re: [PATCH net-next v7 00/10] ipv6: Address ext hdr DoS vulnerabilities
Date: Thu, 5 Feb 2026 18:45:12 -0800 [thread overview]
Message-ID: <20260205184512.306ec46b@kernel.org> (raw)
In-Reply-To: <20260204225154.58245-1-tom@herbertland.com>
On Wed, 4 Feb 2026 14:51:44 -0800 Tom Herbert wrote:
> IPv6 extension headers are defined to be quite open ended with few
> limits. For instance, RFC8200 requires a receiver to process any
> number of extension headers in a packet in any order. This flexibility
> comes at the cost of a potential Denial of Service attack. The only
> thing that might mitigate the DoS attacks is the fact that packets
> with extension headers experience high drop rates on the Internet so
> that a DoS attack based on extension wouldn't be very effective at
> Internet scale.
Patch 10 never arrived..
next prev parent reply other threads:[~2026-02-06 2:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 22:51 [PATCH net-next v7 00/10] ipv6: Address ext hdr DoS vulnerabilities Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 01/10] ipv6: Check of max HBH or DestOp sysctl is zero and drop if it is Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 02/10] ipv6: Cleanup IPv6 TLV definitions Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 03/10] ipv6: Add case for IPV6_TLV_TNL_ENCAP_LIMIT in EH TLV switch Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 04/10] ipv6: Set HBH and DestOpt limits to 2 Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 05/10] ipv6: Document defaults for max_{dst|hbh}_opts_number sysctls Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 06/10] ipv6: Enforce Extension Header ordering Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 07/10] ipv6: Document enforce_ext_hdr_order sysctl Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 08/10] test: Add proto_nums.py in networking selftests Tom Herbert
2026-02-04 22:51 ` [PATCH net-next v7 09/10] test: Add ext_hdr.py " Tom Herbert
2026-02-06 2:45 ` Jakub Kicinski [this message]
[not found] ` <CALx6S3576DLyd18BnFRkaNMhxb-Y3bsy8YJXy3-Q43EQVppEDQ@mail.gmail.com>
2026-02-11 19:16 ` [PATCH net-next v7 00/10] ipv6: Address ext hdr DoS vulnerabilities Jakub Kicinski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260205184512.306ec46b@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=justin.iurman@uliege.be \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=tom@herbertland.com \
--cc=willemdebruijn.kernel@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.