Answer in brief
CVE-2026-98368 records a Unknown severity vulnerability in esp: downgrade zerocopy managed frags before mutating skb frags. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=753f1ca4e1e50248a1b760c9774d6d6b354562cc <2359264f377cdbdef2d95868cc8fb572949e48d3 || >=753f1ca4e1e50248a1b760c9774d6d6b354562cc <69a768c12398cada8528080332c822623fa7064d || >=753f1ca4e1e50248a1b760c9774d6d6b354562cc <6508304ac2c8cdafca2f4ab915df8c707893e134 || >=753f1ca4e1e50248a1b760c9774d6d6b354562cc <6cab554f2c0f28773f712ed3a5479103f42ce844 || >=753f1ca4e1e50248a1b760c9774d6d6b354562cc <0d0845ee61c5df47cc68bc446501f48f71e8dcc6 || >=753f1ca4e1e50248a1b760c9774d6d6b354562cc <f89416eb3db151170a6f3c6dfc5239d26cdce4d2 | 2359264f377cdbdef2d95868cc8fb572949e48d3, 69a768c12398cada8528080332c822623fa7064d, 6508304ac2c8cdafca2f4ab915df8c707893e134, 6cab554f2c0f28773f712ed3a5479103f42ce844, 0d0845ee61c5df47cc68bc446501f48f71e8dcc6, f89416eb3db151170a6f3c6dfc5239d26cdce4d2 |
| Linux/Linuxgeneric | 6.0 | Not reported |
Published upstream
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 6, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 6, 2026
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.
Quoted source text, attributed separately from HOL analysis.