From: Stefano Brivio <sbrivio@redhat.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: Jianlin Shi <jishi@redhat.com>,
Hangbin Liu <liuhangbin@gmail.com>,
Eric Dumazet <edumazet@google.com>,
Stephen Hemminger <stephen@networkplumber.org>,
netdev@vger.kernel.org
Subject: [PATCH net v2 0/2] Fix slab out-of-bounds on insufficient headroom for IPv6 packets
Date: Thu, 6 Dec 2018 19:30:35 +0100 [thread overview]
Message-ID: <cover.1544119954.git.sbrivio@redhat.com> (raw)
Patch 1/2 fixes a slab out-of-bounds occurring with short SCTP packets over
IPv4 over L2TP over IPv6 on a configuration with relatively low HEADER_MAX.
Patch 2/2 makes sure we avoid writing before the allocated buffer in
neigh_hh_output() in case the headroom is enough for the unaligned hardware
header size, but not enough for the aligned one, and that we warn if we hit
this condition.
Stefano Brivio (2):
ipv6: Check available headroom in ip6_xmit() even without options
neighbour: Avoid writing before skb->head in neigh_hh_output()
include/net/neighbour.h | 28 ++++++++++++++++++++++-----
net/ipv6/ip6_output.c | 42 ++++++++++++++++++++---------------------
2 files changed, 44 insertions(+), 26 deletions(-)
--
2.19.2
next reply other threads:[~2018-12-06 18:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-06 18:30 Stefano Brivio [this message]
2018-12-06 18:30 ` [PATCH net v2 1/2] ipv6: Check available headroom in ip6_xmit() even without options Stefano Brivio
2018-12-06 18:30 ` [PATCH net v2 2/2] neighbour: Avoid writing before skb->head in neigh_hh_output() Stefano Brivio
2018-12-08 0:37 ` [PATCH net v2 0/2] Fix slab out-of-bounds on insufficient headroom for IPv6 packets David Miller
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=cover.1544119954.git.sbrivio@redhat.com \
--to=sbrivio@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jishi@redhat.com \
--cc=liuhangbin@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).