CVE Tools

CVE-2026-43284

xfrm: esp: avoid in-place decrypt on shared skb frags

Published: May 8, 2026Updated: Jul 15, 2026 Sources: CVE List NVD BDU csafCWE-123

Description

In the Linux kernel, the following vulnerability has been resolved: xfrm: esp: avoid in-place decrypt on shared skb frags MSG_SPLICE_PAGES can attach pages from a pipe directly to an skb. TCP marks such skbs with SKBFL_SHARED_FRAG after skb_splice_from_iter(), so later paths that may modify packet data can first make a private copy. The IPv4/IPv6 datagram append paths did not set this flag when splicing pages into UDP skbs. That leaves an ESP-in-UDP packet made from shared pipe pages looking like an ordinary uncloned nonlinear skb. ESP input then takes the no-COW fast path for uncloned skbs without a frag_list and decrypts in place over data that is not owned privately by the skb. Mark IPv4/IPv6 datagram splice frags with SKBFL_SHARED_FRAG, matching TCP. Also make ESP input fall back to skb_cow_data() when the flag is present, so ESP does not decrypt externally backed frags in place. Private nonlinear skb frags still use the existing fast path. This intentionally does not change ESP output. In esp_output_head(), the path that appends the ESP trailer to existing skb tailroom without calling skb_cow_data() is not reachable for nonlinear skbs: skb_tailroom() returns zero when skb->data_len is nonzero, while ESP tailen is positive. Thus ESP output will either use the separate destination-frag path or fall back to skb_cow_data().

In plain language

AI Worth attention

This Linux-kernel bug can let a low-privilege local attacker mess with or view protected VPN/ESP packet data during decryption; most small businesses don’t need to worry unless you run a system where untrusted users can log in locally.

Executive summary

In the Linux kernel, xfrm ESP decryption could perform in-place decrypt on shared (externally backed) skb frags, causing sensitive packet data exposure or modification; fixed in multiple kernel commits listed by distributions.

If affected, business impact
Sensitive VPN/ESP data exposureLocal account data tamperingPotential security policy bypassSystem instability risk

What to do now

  1. Check your Linux kernel version on each affected host (e.g., run uname -r).
  2. If your kernel is older than the patched state, plan an update to a kernel version that includes one of the fixes listed for this CVE.
  3. Update systems to include the fix commit(s), using your distribution’s standard security update process (for example, update to the kernel package that contains fix commit a6cb440f274a22456ef3e86b457344f1678f38f9).
  4. Re-check the running kernel version after reboot and confirm the update is active.
  5. Prioritize hosts exposed to local untrusted users (multi-user servers, build boxes, or shared environments) for fastest patching.
Patch / advisory Usually a quick update

CVSS Vector Breakdown

AV:LAC:LPR:LUI:NS:CC:HI:HA:H
Exploitability
AV:LAttack Vector
Local
AC:LAttack Complexity
Low
PR:LPrivileges Required
Low
UI:NUser Interaction
None
Scope
S:CScope
Changed
Impact
C:HConfidentiality
High
I:HIntegrity
High
A:HAvailability
High

Weaknesses

Affected Products

and 7 more affected products View all →

Exploitability

Official Patch Available
Workaround Available

References

and 557 more references View all →
11
See all →

Unlock Complete Vulnerability Intelligence

Get the full picture for CVE-2026-43284 and every CVE in our database. Create a free account — no credit card required.

Create Free Account
Plain-language analysis
Impact assessment and exploitation scenario in plain English
Attack graph visualization
Interactive attack path and kill chain mapping
Exploit details & PoC links
ExploitDB, Metasploit, GitHub PoCs with direct links
Nuclei scanner templates
Ready-to-use vulnerability scanner templates
Full remediation guide
Patch instructions, workarounds, and compliance impact
Interactive AI chat
Ask questions about this vulnerability in natural language
Related vulnerabilities
Semantically similar CVEs and attack patterns
REST API & MCP access
Integrate vulnerability data into your workflows