CVE-2017-1000112

HIGHNVD 7.07.0
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2022-05-14. NVD baseline CVSS 7.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
7.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 21%CVSS: 7.0Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
7.0
EG Score
7.0(medium)
EPSS
97.2%
KEV
Not listed

Published

October 5, 2017

Last Modified

May 13, 2026

Patch Availability(13)

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(13)

Data Freshness Timeline

(refreshed 10× in last 7d / 28× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-07 13:42 UTCEPSS rescore
  2. 2026-07-06 16:24 UTCEPSS rescore
  3. 2026-07-06 16:24 UTCEPSS rescore
  4. 2026-07-06 02:20 UTCEPSS rescore
  5. 2026-07-06 02:20 UTCEPSS rescore
  6. 2026-07-05 02:27 UTCEPSS rescore
  7. 2026-07-04 06:28 UTCEPSS rescore
  8. 2026-07-01 15:02 UTCEPSS rescore
  9. 2026-06-30 23:19 UTCEPSS rescore
  10. 2026-06-30 23:19 UTCEPSS rescore
  11. 2026-06-28 14:04 UTCEPSS rescore
  12. 2026-06-28 04:53 UTCEPSS rescore
  13. 2026-06-27 03:05 UTCEPSS rescore
  14. 2026-06-25 13:47 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-22 23:30 UTCOSV refresh
  18. 2026-06-22 14:23 UTCEPSS rescore
  19. 2026-06-21 01:57 UTCEPSS rescore
  20. 2026-06-21 01:57 UTCEPSS rescore
  21. 2026-06-18 17:50 UTCEPSS rescore
  22. 2026-06-18 17:50 UTCEPSS rescore
  23. 2026-06-17 17:50 UTCEPSS rescore
  24. 2026-06-17 17:50 UTCEPSS rescore
  25. 2026-06-16 17:50 UTCEPSS rescore
Show 24 more
  1. 2026-06-15 17:45 UTCEPSS rescore
  2. 2026-06-12 23:09 UTCEPSS rescore
  3. 2026-06-11 13:57 UTCEPSS rescore
  4. 2026-06-06 13:45 UTCEPSS rescore
  5. 2026-06-06 13:45 UTCEPSS rescore
  6. 2026-06-05 22:44 UTCEPSS rescore
  7. 2026-06-05 16:57 UTCOSV refresh
  8. 2026-06-05 06:08 UTCEPSS rescore
  9. 2026-06-05 06:08 UTCEPSS rescore
  10. 2026-05-31 00:14 UTCEPSS rescore
  11. 2026-05-28 13:42 UTCEPSS rescore
  12. 2026-05-28 13:42 UTCEPSS rescore
  13. 2026-05-27 13:38 UTCEPSS rescore
  14. 2026-05-27 13:38 UTCEPSS rescore
  15. 2026-05-22 21:15 UTCEPSS rescore
  16. 2026-05-22 09:15 UTCEG score recompute
  17. 2026-05-22 09:15 UTCVendor advisory
  18. 2026-05-22 09:15 UTCGHSA enrichment
  19. 2026-05-20 22:37 UTCEPSS rescore
  20. 2026-05-20 22:37 UTCEPSS rescore
  21. 2026-05-20 22:37 UTCEPSS rescore
  22. 2026-05-18 21:30 UTCEPSS rescore
  23. 2026-05-18 21:30 UTCEPSS rescore
  24. 2026-05-18 21:30 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (1 Metasploit module) (3 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-47169
    First seen Dec 29, 2018

    Linux Kernel < 4.4.0/ < 4.8.0 (Ubuntu 14.04/16.04 / Linux Mint 17/18 / Zorin) - Local Privilege Escalation (KASLR / SMEP)

    Open source ↗
  • Exploit-DBEDB-45147✓ verified
    First seen Aug 3, 2018

    Linux Kernel - UDP Fragmentation Offset 'UFO' Privilege Escalation (Metasploit)

    Open source ↗
  • Exploit-DBEDB-43418✓ verified
    First seen Aug 13, 2017

    Linux Kernel < 4.4.0-83 / < 4.8.0-58 (Ubuntu 14.04/16.04) - Local Privilege Escalation (KASLR / SMEP)

    Open source ↗
  • Metasploitexploit/linux/local/ufo_privilege_escalation✓ verified
    First seen Aug 10, 2017

    Linux Kernel UDP Fragmentation Offset (UFO) Privilege Escalation

    Open source ↗

Frequently asked(5)

What is CVE-2017-1000112?
CVE-2017-1000112 is a high vulnerability published on October 5, 2017. 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.…
When was CVE-2017-1000112 disclosed?
CVE-2017-1000112 was first published in the National Vulnerability Database on October 5, 2017, with the most recent update on May 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-1000112 actively exploited?
CVE-2017-1000112 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 97.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2017-1000112?
CVE-2017-1000112 has a CVSS v3 base score of 7.0 (NVD).
How do I remediate CVE-2017-1000112?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-1000112, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-1000112

Explore →

Is Your Infrastructure Affected by CVE-2017-1000112?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.