CVE-2026-98368

esp: downgrade zerocopy managed frags before mutating skb frags

  • High 7.8

Description

In the Linux kernel, the following vulnerability has been resolved: esp: downgrade zerocopy managed frags before mutating skb frags On the out-of-place output path (esp->inplace == false) ESP rewrites the skb frag array: esp_output_head() appends a trailer frag and esp_output_tail() replaces the frags with a destination page, both referenced with get_page(). When the skb carries zerocopy managed frags (SKBFL_MANAGED_FRAG_REFS) the payload frags are owned by the ubuf and must not be referenced or unreferenced individually, but ESP mutates the frag array without ever downgrading the skb. This breaks the managed-frag invariant two ways: - esp_ssg_unref() walks the source scatterlist and drops a page reference for every frag, including the ubuf-owned payload frags, pushing their refcount below the GUP pin bias while the pages are still pinned, i.e. a use-after-free of the zerocopy pages; - esp_output_tail() installs its destination page as frag 0 with get_page() but leaves SKBFL_MANAGED_FRAG_REFS set, so skb_release_data() takes the skip_unref branch and never drops that reference, leaking the x->xfrag page at packet rate. Fix this the way every other frag-mutating site does (__ip_append_data(), __ip6_append_data(), tcp_sendmsg_locked()) and call skb_zcopy_downgrade_managed() before ESP touches the frag array: it takes a real reference on each existing frag and clears SKBFL_MANAGED_FRAG_REFS, so the per-frag unref in esp_ssg_unref() and the frag release in skb_release_data() are both balanced and no mixed-ownership frag array is left behind.

Key facts

Published
6 Oct 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.117% likely to be exploited in the next 30 days, higher than 1.724% of CVEs (scores for 17 Nov 2026)

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 7.8CVSS 3.1, Highfrom the CNA (Linux)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to but excluding 2359264f377cdbdef2d95868cc8fb572949e48d3 (affected)
  • 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to but excluding 69a768c12398cada8528080332c822623fa7064d (affected)
  • 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to but excluding 6508304ac2c8cdafca2f4ab915df8c707893e134 (affected)
  • 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to but excluding 6cab554f2c0f28773f712ed3a5479103f42ce844 (affected)
  • 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to but excluding 0d0845ee61c5df47cc68bc446501f48f71e8dcc6 (affected)
  • 753f1ca4e1e50248a1b760c9774d6d6b354562cc up to but excluding f89416eb3db151170a6f3c6dfc5239d26cdce4d2 (affected)
LinuxLinux
  • Default status: affected
  • 6.0 (affected)
  • 0 up to but excluding 6.0 (unaffected)
  • 6.1.189 up to and including 6.1.* (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.112 up to and including 6.12.* (unaffected)
  • 6.18.54 up to and including 6.18.* (unaffected)
  • 7.2.8 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 6 Oct 2026 Published

References