CVE-2026-98368esp: downgrade zerocopy managed frags before mutating skb frags
Updated under an hour ago ()
Does this affect you?
It affects Linux. Add what you run to find out whether that includes you.
EPSS puts the chance of exploitation in the next 30 days at 0.13%, higher than 2% of scored CVEs.
Do this next
Free account, 1 product
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.
- CVSS
- 7.8 HIGH (v3.1, CNA)CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Weakness (CWE)
- Not given
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- 0.13% (percentile 2)
- Assigned by
- Linux
- NVD analysis
- Received
- Record last updated
- Oct 19, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
Linux Linux linux:linux (from the name) | from 753f1ca4e1e50248a1b760c9774d6d6b354562cc before 2359264f377cdbdef2d95868cc8fb572949e48d3; 753f1ca4e1e50248a1b760c9774d6d6b354562cc builds before 69a768c12398cada8528080332c822623fa7064d; from 753f1ca4e1e50248a1b760c9774d6d6b354562cc before 6508304ac2c8cdafca2f4ab915df8c707893e134; 753f1ca4e1e50248a1b760c9774d6d6b354562cc builds before 6cab554f2c0f28773f712ed3a5479103f42ce844; 753f1ca4e1e50248a1b760c9774d6d6b354562cc builds before 0d0845ee61c5df47cc68bc446501f48f71e8dcc6; from 753f1ca4e1e50248a1b760c9774d6d6b354562cc before f89416eb3db151170a6f3c6dfc5239d26cdce4d2 | CNA record |
References
- https://git.kernel.org/stable/c/2359264f377cdbdef2d95868cc8fb572949e48d3
- https://git.kernel.org/stable/c/69a768c12398cada8528080332c822623fa7064d
- https://git.kernel.org/stable/c/6508304ac2c8cdafca2f4ab915df8c707893e134
- https://git.kernel.org/stable/c/6cab554f2c0f28773f712ed3a5479103f42ce844
- https://git.kernel.org/stable/c/0d0845ee61c5df47cc68bc446501f48f71e8dcc6
- https://git.kernel.org/stable/c/f89416eb3db151170a6f3c6dfc5239d26cdce4d2
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.