Bug 1707358 (CVE-2019-11683) - CVE-2019-11683 kernel: udp_gro_receive_segment in net/ipv4/udp_offload.c allows denial of service or other unspecified impact via UDP packets with 0 payload
Summary: CVE-2019-11683 kernel: udp_gro_receive_segment in net/ipv4/udp_offload.c allo...
Keywords:
Status: CLOSED NOTABUG
Alias: CVE-2019-11683
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1707359
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-07 11:24 UTC by msiddiqu
Modified: 2019-09-29 15:13 UTC (History)
42 users (show)

Fixed In Version: kernel 5.0.13
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-06-10 10:55:08 UTC


Attachments (Terms of Use)

Description msiddiqu 2019-05-07 11:24:31 UTC
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.

Introduced in:

http://git.kernel.org/linus/e20cf8d3f1f763ad28a9cb3b41305b8a8a42653e

Upstream patch:

https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=4dd2b82d5adfbe0b1587ccad7a8f76d826120f37

References:

https://www.spinics.net/lists/netdev/msg568315.html
http://www.openwall.com/lists/oss-security/2019/05/02/1
https://www.openwall.com/lists/oss-security/2019/05/05/4
https://seclists.org/oss-sec/2019/q2/86
https://cdn.kernel.org/pub/linux/kernel/v5.x/ChangeLog-5.0.13

Comment 1 msiddiqu 2019-05-07 11:24:52 UTC
Created kernel tracking bugs for this issue:

Affects: fedora-all [bug 1707359]

Comment 2 msiddiqu 2019-05-08 09:55:06 UTC
Statement:

This flaw did not affect the versions of kernel as shipped with Red Hat Enterprise Linux 5, 6, 7 and 8.


Note You need to log in before you can comment on or make changes to this bug.