CVE-2026-43284

Modified
Published: 08 May 2026, 07:21
Last modified:14 Jun 2026, 17:44

Vulnerability Summary

Overall Risk (default)
high
64/100
CVSS Score
8.8 HIGH
v3.1 (cve.org)
EPSS Score
92.16% CRITICAL
92% probability +74.71%
KEV
Not listed
Ransomware
No reports
Public exploits
4 found
Dark Web
Not detected

Timeline

08 May 2026, 07:21
Published
Vulnerability first disclosed
14 Jun 2026, 17:44
Last Modified
Vulnerability information updated

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().

CVSS Metrics

  • v3.1HIGHScore: 8.8CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS Trends

Current EPSS score: 92.16% Percentile: 100%

Techniques & Countermeasures

  • CWE-416Use After Free

    The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.

  • CWE-123Write-what-where Condition

    Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

Affected Systems

  • linuxlinux

    ≥ 7da0dde68486b2d5bd7c689a9b327b77efecdfd0, < 50ed1e7873100f77abad20fd31c51029bc49cd03 | ≥ 7da0dde68486b2d5bd7c689a9b327b77efecdfd0, < b54edf1e9a3fd3491bdcb82a21f8d21315271e0d | ≥ 7da0dde68486b2d5bd7c689a9b327b77efecdfd0, < 71a1d9d985d26716f74d21f18ee8cac821b06e97 | ≥ 7da0dde68486b2d5bd7c689a9b327b77efecdfd0, < 52646cbd00e765a6db9c3afe9535f26218276034 | 6.5 | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < a6cb440f274a22456ef3e86b457344f1678f38f9 | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < ab8b995323e5237041472d07e5055f5f7dcdf15b | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < fe785bb3a8096dffcc4048a85cd0c83337eeecad | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < 5d55c7336f8032d434adcc5fab987ccc93a44aec | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < 8253aab4659ca16116b522203c2a6b18dccacea7 | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < 50ed1e7873100f77abad20fd31c51029bc49cd03 | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < b54edf1e9a3fd3491bdcb82a21f8d21315271e0d | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < 71a1d9d985d26716f74d21f18ee8cac821b06e97 | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < 52646cbd00e765a6db9c3afe9535f26218276034 | ≥ cac2661c53f35cbe651bef9b07026a5a05ab8ce0, < f4c50a4034e62ab75f1d5cdd191dd5f9c77fdff4 | 4.11

  • linuxlinux_kernel

    ≥ 4.11, < 5.10.255 | ≥ 5.12, < 5.15.205 | ≥ 5.16, < 6.1.171 | ≥ 6.2, < 6.6.138 | ≥ 6.7, < 6.12.87 | ≥ 6.13, < 6.18.28 | ≥ 7.0, < 7.0.5

References (17)