CVE-2026-98368·Kernel vulnerability
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.
- Severity
- high
- Software
- Kernel
- Fixed in
- 6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8, 7.3
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.13% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Read the two together. CVE-2026-98368 scores 7.8 on CVSS, so a successful attack would be serious — but at 0.13%, almost nobody is currently attempting it. That is a different situation from a flaw under mass exploitation, and it is usually the difference between patching on your next maintenance window and patching tonight.
How to fix this CVE
Update your Linux kernel to a patched version that includes the zerocopy managed frags fix. Users running stable branches should upgrade to kernel 6.1.189, 6.6.158, 6.12.112, 6.18.54, or 7.2.8 depending on their current kernel line. Alternatively, install your Linux distribution's patched kernel package, which will backport the fix without requiring a jump to mainline.
sudo dnf update kernel kernel-develDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check your current kernel version with `uname -r` and compare against the fixed versions (6.1.189, 6.6.158, 6.12.112, 6.18.54, 7.2.8, or 7.3+)
- Step 2: Verify if your system uses ESP (Encapsulating Security Payload) for IPsec tunnels by checking `grep -i esp /proc/net/xfrm_stat` or `ip xfrm policy list | grep esp`
- Step 3: Monitor kernel logs for memory corruption or page reference errors using `sudo dmesg | grep -i 'use.after.free\|page.refcount\|skb_release'`
- Step 4: After patching, confirm the new kernel version is running with `uname -r` and reboot if necessary with `sudo reboot`
FAQ
What is CVE-2026-98368?
This is a use-after-free vulnerability in the Linux kernel's ESP (Encapsulating Security Payload) subsystem that occurs when processing packets with zerocopy-managed buffer fragments. The ESP code incorrectly manipulates the socket buffer's fragment array without properly downgrading managed references, leading to double-frees and memory corruption.
Is CVE-2026-98368 being actively exploited?
No, CVE-2026-98368 is not listed as actively exploited in CISA's Known Exploited Vulnerabilities catalog, and no public exploits are currently available.
What versions of Kernel are affected by CVE-2026-98368?
All kernel versions prior to the fixed releases are affected: upgrade to 6.1.189+, 6.6.158+, 6.12.112+, 6.18.54+, 7.2.8+, or mainline 7.3+.
How do I check if my server is vulnerable to CVE-2026-98368?
Run `uname -r` to get your kernel version. If it's earlier than one of the fixed releases in your branch (6.1.189, 6.6.158, 6.12.112, 6.18.54, or 7.2.8), and you use IPsec with ESP, your system is vulnerable.
Does Defensia detect CVE-2026-98368?
Yes — Defensia's CVE advisory scanner compares installed kernel versions against the NVD database. If the Linux kernel is installed on a monitored server, CVE-2026-98368 will appear in your dashboard with remediation steps and fixed version details.
Related Kernel CVEs
References
- https://git.kernel.org/stable/c/0d0845ee61c5df47cc68bc446501f48f71e8dcc6
- https://git.kernel.org/stable/c/2359264f377cdbdef2d95868cc8fb572949e48d3
- https://git.kernel.org/stable/c/6508304ac2c8cdafca2f4ab915df8c707893e134
- https://git.kernel.org/stable/c/69a768c12398cada8528080332c822623fa7064d
- https://git.kernel.org/stable/c/6cab554f2c0f28773f712ed3a5479103f42ce844
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-98368. Free for 1 server.
Get started free