CVE-2016-7039: High severity oracle linux vulnerability
Linux kernel built with the 802.1Q/802.1ad VLAN(CONFIGVLAN8021Q) OR Virtual eXtensible Local Area Network(CONFIGVXLAN) with Transparent Ethernet Bridging(TEB) GRO support, is vulnerable to a stack overflow issue. It could occur while receiving large packets via GRO path; As an unlimited recursion could unfold in both VLAN and TEB modules, leading to a stack corruption in the kernel.
A remote user could use this falw to cause kernel panic by sending maliciously crafted packets to a server that has GRO enabled.
Additional requirement for attacking VLAN is to have 8021q module loaded. Additional requirement for attacking TEB is to have increased MTU.
Upstream patch --------------- -> https://patchwork.ozlabs.org/patch/680412/
Other sources
The IP stack in the Linux kernel through 4.8.2 allows remote attackers to cause a denial of service (stack consumption and panic) or possibly have unspecified other impact by triggering use of the GRO path for large crafted packets, as demonstrated by packets that contain only VLAN headers, a related issue to CVE-2016-8666.
— MITRE
Affected Software
Remediation
Patch Available
Patch Available
Event History
Frequently Asked Questions
What is the severity of CVE-2016-7039?
CVE-2016-7039 is classified as a high severity vulnerability due to the potential for stack overflow leading to system crashes.
How does CVE-2016-7039 affect the Linux kernel?
CVE-2016-7039 affects the Linux kernel by allowing a stack overflow when large packets are received via the GRO path with TEB support.
Which versions of Oracle Linux are impacted by CVE-2016-7039?
Oracle Linux versions 6 and 7 are impacted by CVE-2016-7039.
What versions of the Linux kernel are vulnerable to CVE-2016-7039?
Linux kernel versions 4.0 to 4.1.37, 4.2 to 4.4.32, and 4.5 to 4.8.8 are vulnerable to CVE-2016-7039.
How can I mitigate the risks associated with CVE-2016-7039?
Risks associated with CVE-2016-7039 can be mitigated by applying kernel patches or upgrading to versions that have addressed this vulnerability.