PoC Monitor
← All CVEs
CVE-2026-98368published 6 Oct 2026 08:46 UTCData: JSON · API

Linux

esp: downgrade zerocopy managed frags before mutating skb frags

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.8high · scored by CNA
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Linux Linux
  • >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc, < 2359264f377cdbdef2d95868cc8fb572949e48d3
  • >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc, < 69a768c12398cada8528080332c822623fa7064d
  • >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc, < 6508304ac2c8cdafca2f4ab915df8c707893e134
  • >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc, < 6cab554f2c0f28773f712ed3a5479103f42ce844
  • >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc, < 0d0845ee61c5df47cc68bc446501f48f71e8dcc6
  • >= 753f1ca4e1e50248a1b760c9774d6d6b354562cc, < f89416eb3db151170a6f3c6dfc5239d26cdce4d2

Fixed in 2359264f377cdbdef2d95868cc8fb572949e48d3, 69a768c12398cada8528080332c822623fa7064d, 6508304ac2c8cdafca2f4ab915df8c707893e134, 6cab554f2c0f28773f712ed3a5479103f42ce844, 0d0845ee61c5df47cc68bc446501f48f71e8dcc6, f89416eb3db151170a6f3c6dfc5239d26cdce4d2

Linux Linux
  • 6.0

Fixed in 0, 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8, 7.3

Mitigation

Upgrade Linux to 2359264f377cdbdef2d95868cc8fb572949e48d3 or 69a768c12398cada8528080332c822623fa7064d or 6508304ac2c8cdafca2f4ab915df8c707893e134 or 6cab554f2c0f28773f712ed3a5479103f42ce844 or 0d0845ee61c5df47cc68bc446501f48f71e8dcc6 or f89416eb3db151170a6f3c6dfc5239d26cdce4d2 or later.

Upgrade Linux to 0 or 6.1.189 or 6.6.158 or 6.12.112 or 6.18.54 or 7.2.8 or 7.3 or later.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published6 Oct 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.