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 E
Casky was already ahead
This CVE exploits attack patterns that Casky's 0matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.
CVE-2026-43284 is a high-severity vulnerability in the Linux kernel's xfrm (IPsec transform) subsystem affecting ESP (Encapsulating Security Payload) over UDP implementations. The vulnerability stems from the kernel's failure to properly mark shared socket buffer fragments as protected when data is spliced directly from pipes into UDP skbs. When MSG_SPLICE_PAGES attaches pipe pages to network packets, the kernel should flag these as SKBFL_SHARED_FRAG to prevent in-place modification. Because the IPv4/IPv6 datagram append paths omit this critical flag, ESP decryption operations can corrupt shared memory pages—potentially affecting any system handling ESP-in-UDP traffic, particularly VPN implementations, containerized environments, and network appliances relying on kernel-space encryption.
While CVE-2026-43284 lacks mapped MITRE ATT&CK techniques and currently shows no Casky skill matches, the vulnerability's detection would benefit from extended reasoning across kernel memory safety patterns and IPsec protocol anomalies. Practitioners using Casky would observe findings centered on CWE-123 (Write-What-Where condition) manifestations: unexpected memory corruption in packet processing paths, data integrity failures in encrypted UDP streams, and race conditions between packet splicing and cryptographic operations. Security teams should monitor for kernel crash dumps showing xfrm/ESP stack traces, packet processing anomalies in VPN/IPsec contexts, and potential denial-of-service indicators when shared buffer fragments are inadvertently modified during decryption operations.
Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →
Casky has 0 skills that investigate the attack patterns behind CVE-2026-43284. Run one and get CVSS-scored findings in 3 minutes.
Run the skill that detects this →© 2026 Casky.AI, Inc. · AI Security Investigation