# CVE-2017-1000112: Memory corruption in n/a > A race condition in the Linux kernel network stack allows memory corruption via UFO packet handling, potentially enabling local privilege escalation or code execution. - **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 4 Oct 2017 - **Updated:** 5 Aug 2024 - **Also known as:** DEBIAN-CVE-2017-1000112, GHSA-r7cm-47vv-77vj, RHSA-2019:1931, RHSA-2019:1932, SUSE-SU-2017:2423-1, SUSE-SU-2017:2424-1, SUSE-SU-2017:2436-1, SUSE-SU-2017:2437-1, SUSE-SU-2017:2438-1, SUSE-SU-2017:2438-2, SUSE-SU-2017:2439-1, SUSE-SU-2017:2440-1, SUSE-SU-2017:2441-1, SUSE-SU-2017:2442-1, SUSE-SU-2017:2443-1, SUSE-SU-2017:2454-1, SUSE-SU-2017:2455-1, SUSE-SU-2017:2456-1, SUSE-SU-2017:2457-1, SUSE-SU-2017:2458-1, SUSE-SU-2017:2464-1, SUSE-SU-2017:2465-1, SUSE-SU-2017:2467-1, SUSE-SU-2017:2469-1, SUSE-SU-2017:2471-1, SUSE-SU-2017:2472-1, SUSE-SU-2017:2473-1, SUSE-SU-2017:2474-1, SUSE-SU-2017:2498-1, SUSE-SU-2017:2499-1, SUSE-SU-2017:2500-1, SUSE-SU-2017:2506-1, SUSE-SU-2017:2508-1, SUSE-SU-2017:2509-1, SUSE-SU-2017:2510-1, SUSE-SU-2017:2511-1, UBUNTU-CVE-2017-1000112 ## What is CVE-2017-1000112? CVE-2017-1000112 is a high-severity memory corruption vulnerability in Linux kernel, published on 4 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Linux kernel: Exploitable memory corruption due to UFO to non-UFO path switch. When building a UFO packet with MSG_MORE __ip_append_data() calls ip_ufo_append_data() 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 = skb_prev->len - maxfraglen. Fraggap can exceed MTU, causing copy = datalen - transhdrlen - fraggap to become negative. Subsequently skb_copy_and_csum_bits() 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. Weakness: CWE-362 (Concurrent Execution using Shared Resource with Improper Synchronization) ## Which versions are affected by CVE-2017-1000112? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `kernel` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-PAE` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-PAE-debuginfo` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-PAE-devel` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-debug` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-debug-debuginfo` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-debug-devel` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-debuginfo` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-debuginfo-common` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-devel` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-doc` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-headers` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-xen` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-xen-debuginfo` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel-xen-devel` | Red Hat:rhel_aus:5.9 | All versions | 0:2.6.18-348.44.1.el5 | | `kernel` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-PAE` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-PAE-debuginfo` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-PAE-devel` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-debug` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-debug-debuginfo` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-debug-devel` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-debuginfo` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-debuginfo-common` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-devel` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-doc` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-headers` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-kdump` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-kdump-debuginfo` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-kdump-devel` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-xen` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-xen-debuginfo` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kernel-xen-devel` | Red Hat:rhel_els:5 | All versions | 0:2.6.18-438.el5 | | `kgraft-patch-SLE12-SP2_Update_0` | SUSE:Linux Enterprise Live Patching 12 | All versions | 9-18.10.1 | | `kgraft-patch-SLE12-SP2_Update_1` | SUSE:Linux Enterprise Live Patching 12 | All versions | 9-2.1 | | `kgraft-patch-SLE12-SP2_Update_10` | SUSE:Linux Enterprise Live Patching 12 | All versions | 3-2.1 | | `kgraft-patch-SLE12-SP2_Update_11` | SUSE:Linux Enterprise Live Patching 12 | All versions | 2-2.1 | | `kgraft-patch-SLE12-SP2_Update_12` | SUSE:Linux Enterprise Live Patching 12 | All versions | 2-2.1 | | `kgraft-patch-SLE12-SP2_Update_2` | SUSE:Linux Enterprise Live Patching 12 | All versions | 8-2.1 | | `kgraft-patch-SLE12-SP2_Update_3` | SUSE:Linux Enterprise Live Patching 12 | All versions | 8-2.1 | Products: Linux kernel. ## How do I fix CVE-2017-1000112? Apply the vendor's patch. ## Is CVE-2017-1000112 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1000112 exists. Public exploit code: - POE code for CVE-2017-1000112 adapted to both funtion on a specific VM and Escape a Docker (github_poc): https://github.com/ol0273st-s/CVE-2017-1000112-Adpated - Exploit work Privilege Escalation CVE-2017-1000112 (github_poc): https://github.com/IT19083124/SNP-Assignment - https://github.com/Spydomain/CVE-2017-1000112-PoC (github_poc): https://github.com/Spydomain/CVE-2017-1000112-PoC - Linux Kernel UDP Fragmentation Offset (UFO) Privilege Escalation (metasploit) - Linux Kernel < 4.4.0-83 / < 4.8.0-58 (Ubuntu 14.04/16.04) - Local Privilege Escalation (KASLR / SMEP) (exploitdb) - Linux Kernel - UDP Fragmentation Offset 'UFO' Privilege Escalation (Metasploit) (exploitdb) ## Other vulnerabilities in Linux kernel - [CVE-2026-53266](https://insights.sbomify.com/CVE-2026-53266/): Linux Kernel Out-of-Bounds Write (high 8.8, exploited in the wild) - [CVE-2013-6282](https://insights.sbomify.com/CVE-2013-6282/): Linux Kernel Improper Input Validation (high 8.8, exploited in the wild) - [CVE-2022-0185](https://insights.sbomify.com/CVE-2022-0185/): Linux Kernel Heap-Based Buffer Overflow (high 8.4, exploited in the wild) - [CVE-2013-2094](https://insights.sbomify.com/CVE-2013-2094/): Linux Kernel Privilege Escalation (high 8.4, exploited in the wild) - [CVE-2026-53362](https://insights.sbomify.com/CVE-2026-53362/): Linux Kernel Unspecified (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2017-1000112 and fix it if it is affected. What it is: CVE-2017-1000112 is a high-severity memory corruption vulnerability in Linux kernel, published on 4 Oct 2017. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-1000112 exists. Affected product: Linux kernel. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2017-1000112/ (Markdown: https://insights.sbomify.com/CVE-2017-1000112/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2017-1000112 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-1000112 - OSV: https://osv.dev/vulnerability/CVE-2017-1000112 --- From sbomify Insights: https://insights.sbomify.com/CVE-2017-1000112/ Summaries are generated and may contain mistakes; the official description above is the record.