From: Davide Caratti <dcaratti@redhat.com>
To: Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org
Subject: [PATCH net resend 0/2] fix stack OOB read while fragmenting IPv4 packets
Date: Wed, 28 Apr 2021 15:23:00 +0200 [thread overview]
Message-ID: <cover.1619615320.git.dcaratti@redhat.com> (raw)
- patch 1/2 fixes openvswitch IPv4 fragmentation, that does a stack OOB
read after commit d52e5a7e7ca4 ("ipv4: lock mtu in fnhe when received
PMTU < net.ipv4.route.min_pmt")
- patch 2/2 fixes the same issue in TC 'sch_frag' code
Davide Caratti (2):
openvswitch: fix stack OOB read while fragmenting IPv4 packets
net/sched: sch_frag: fix stack OOB read while fragmenting IPv4 packets
net/openvswitch/actions.c | 8 ++++----
net/sched/sch_frag.c | 8 ++++----
2 files changed, 8 insertions(+), 8 deletions(-)
--
2.30.2
next reply other threads:[~2021-04-28 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-28 13:23 Davide Caratti [this message]
2021-04-28 13:23 ` [PATCH net resend 1/2] openvswitch: fix stack OOB read while fragmenting IPv4 packets Davide Caratti
2021-04-28 13:23 ` [PATCH net resend 2/2] net/sched: sch_frag: " Davide Caratti
2021-04-29 22:40 ` [PATCH net resend 0/2] " patchwork-bot+netdevbpf
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.1619615320.git.dcaratti@redhat.com \
--to=dcaratti@redhat.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.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).