From: Eric Dumazet <eric.dumazet@gmail.com>
To: Reindl Harald <h.reindl@thelounge.net>, netdev@vger.kernel.org
Subject: Re: CVE-2019-11683
Date: Sat, 4 May 2019 12:06:59 -0400 [thread overview]
Message-ID: <0ca5c3b7-49e5-6fdd-13ba-4aaee72f2060@gmail.com> (raw)
In-Reply-To: <7a1c575b-b341-261c-1f22-92d656d6d9ae@thelounge.net>
On 5/4/19 11:49 AM, Reindl Harald wrote:
> is this fixed in 5.0.12 and just not visible in the changelog?
>
> because if not there's no poiunt to reboot a over a long time randomly
> crahsing firewall setup which *appears* stable now after replace "LOG"
> with "NFLOG" and remove --reap from the xt_recent rules
>
> ----------------------
>
> https://www.openwall.com/lists/oss-security/2019/05/02/1
>
> syzbot has reported a remotely triggerable memory corruption in the
> Linux kernel. It's been introduced quite recently in e20cf8d3f1f7
> ("udp: implement GRO for plain UDP sockets.") and only affects the 5.0
> (stable) release (so the name is a bit overhyped :).
>
> CVE-2019-11683 description:
>
> udp_gro_receive_segment in net/ipv4/udp_offload.c in the Linux kernel
> 5.x through 5.0.11 allows remote attackers to cause a denial of
> service (slab-out-of-bounds memory corruption) or possibly have
> unspecified other impact via UDP packets with a 0 payload, because of
> mishandling of padded packets, aka the "GRO packet of death" issue.
>
> Fix (not yet upstream):
>
> https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=4dd2b82d5adfbe0b1587ccad7a8f76d826120f37
>
> ----------------------
>
> https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.11
> https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.12
>
The missing part in this CVE is that this is not remotely triggerable as-is.
UDP receiver has to opt-in for GRO, and I doubt any application does this currently.
next prev parent reply other threads:[~2019-05-04 16:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-04 15:49 CVE-2019-11683 Reindl Harald
2019-05-04 16:06 ` Eric Dumazet [this message]
2019-05-04 16:13 ` CVE-2019-11683 Reindl Harald
2019-05-04 16:32 ` CVE-2019-11683 Eric Dumazet
2019-05-04 16:39 ` CVE-2019-11683 Reindl Harald
2019-05-04 16:42 ` CVE-2019-11683 Stephen Hemminger
2019-05-04 16:43 ` CVE-2019-11683 Eric Dumazet
2019-05-04 16:47 ` CVE-2019-11683 Reindl Harald
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=0ca5c3b7-49e5-6fdd-13ba-4aaee72f2060@gmail.com \
--to=eric.dumazet@gmail.com \
--cc=h.reindl@thelounge.net \
--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