CVE-2017-1000112: Race Condition

Published Aug 8, 2017
·
Updated

A memory corruption issue was found in the Linux kernel.

When building a UFO packet with MSGMORE ipappenddata() calls ipufoappenddata() to append. However in between two send() calls, the append path can be switched from UFO to non-UFO one, which leads to a memory corruption.

In case UFO packet lengths exceeds MTU, copy = maxfraglen - skb->len becomes negative on the non-UFO path and the branch to allocate new skb is taken. This triggers fragmentation and computation of fraggap = skbprev->len - maxfraglen. Fraggap can exceed MTU, causing copy = datalen - transhdrlen - fraggap to become negative. Subsequently skbcopyandcsumbits() writes out-of-bounds.

Introducing commit:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=e89e9cf539a2

Other sources

Linux kernel: Exploitable memory corruption due to UFO to non-UFO path switch. When building a UFO packet with MSGMORE ipappenddata() calls ipufoappenddata() to append. However in between two send() calls, the append path can be switched from UFO to non-UFO one, which leads to a memory corruption. In case UFO packet lengths exceeds MTU, copy = maxfraglen - skb->len becomes negative on the non-UFO path and the branch to allocate new skb is taken. This triggers fragmentation and computation of fraggap = skbprev->len - maxfraglen. Fraggap can exceed MTU, causing copy = datalen - transhdrlen - fraggap to become negative. Subsequently skbcopyandcsumbits() writes out-of-bounds. A similar issue is present in IPv6 code. The bug was introduced in e89e9cf539a2 ("[IPv4/IPv6]: UFO Scatter-gather approach") on Oct 18 2005.

Affected Software

7 affected componentsFixes available
debian/linux
4.19.249-24.19.289-25.10.197-15.10.205-26.1.66-16.1.69-16.5.13-16.6.9-1
Linux Linux kernel>=2.6.15<3.10.108
Linux Linux kernel>=3.11<3.16.47
Linux Linux kernel>=3.17<3.18.65
Linux Linux kernel>=3.19<4.4.82
Linux Linux kernel>=4.5<4.9.43
Linux Linux kernel>=4.10<4.12.7

Remediation

Event History

Aug 8, 2017
Data Sourced
via Red Hat·10:49 AM
DescriptionSeverityAffected Software
Oct 4, 2017
CVE Published
via MITRE·01:00 AM
Data Sourced
via MITRE·01:00 AM
Description

Frequently Asked Questions

1

What is the severity of CVE-2017-1000112?

CVE-2017-1000112 has been classified as a high-severity vulnerability due to the potential for memory corruption.

2

How do I fix CVE-2017-1000112?

To remediate CVE-2017-1000112, you should upgrade to a patched version of the Linux kernel, specifically versions 4.19.249-2, 5.10.197-1, or later.

3

Which Linux kernel versions are affected by CVE-2017-1000112?

CVE-2017-1000112 affects Linux kernel versions between 2.6.15 and 4.12.7.

4

What can happen if I am vulnerable to CVE-2017-1000112?

If your system is vulnerable to CVE-2017-1000112, it could lead to memory corruption that may be exploited by attackers to cause system instability or execute arbitrary code.

5

Is CVE-2017-1000112 specific to a certain distribution of Linux?

No, CVE-2017-1000112 is a vulnerability found in the Linux kernel and can affect multiple distributions that utilize the affected kernel versions.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203