← Back to browse · API

CVE-2026-43284

Severity
HIGH
CVSS
8.8
EPSS
0.93235
Risk score
67.83
CISA KEV
No
PoC
Yes
Published
2026-05-08
Modified
2026-08-05
First seen
2026-08-06
Aliases
CNVD-2026-21358, EUVD-2026-28535, GHSA-MMW8-MXMC-8W2R
Products
Linux Linux kernel >=4.11,<5.10.255, Linux Linux kernel >=5.12,<5.15.205, Linux Linux kernel >=5.16,<6.1.171, Linux Linux kernel >=6.13,<6.18.28, Linux Linux kernel >=6.2,<6.6.138, Linux Linux kernel >=6.7,<6.12.87, Linux Linux kernel >=7.0,<7.0.5, Linux:Linux 4.11, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <50ed1e7873100f77abad20fd31c51029bc49cd03, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <52646cbd00e765a6db9c3afe9535f26218276034, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <5d55c7336f8032d434adcc5fab987ccc93a44aec, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <71a1d9d985d26716f74d21f18ee8cac821b06e97, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <8253aab4659ca16116b522203c2a6b18dccacea7, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <a6cb440f274a22456ef3e86b457344f1678f38f9, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <ab8b995323e5237041472d07e5055f5f7dcdf15b, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <b54edf1e9a3fd3491bdcb82a21f8d21315271e0d, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <f4c50a4034e62ab75f1d5cdd191dd5f9c77fdff4, Linux:Linux cac2661c53f35cbe651bef9b07026a5a05ab8ce0 <fe785bb3a8096dffcc4048a85cd0c83337eeecad, Linux:Linux patch: 0, Linux:Linux patch: 5.10.255, Linux:Linux patch: 5.15.205, Linux:Linux patch: 5.15.206, Linux:Linux patch: 6.1.171, Linux:Linux patch: 6.1.172, Linux:Linux patch: 6.12.87, Linux:Linux patch: 6.18.28, Linux:Linux patch: 6.6.138, Linux:Linux patch: 7.0.5, Linux:Linux patch: 7.1, linux, suse, ubuntu, unix
Sources
cnvd CNVD-2026-21358
github 02517c60d0c89df8226fa9fb|CVE-2026-43284
github 21602d62a72f27b43cffe237|CVE-2026-43284
packetstorm 57db8f810f92fa2da22b8773|CVE-2026-43284
github dafe85faefa240ce615dc5b3|CVE-2026-43284
github b0a7e3cafd5fd3a1ec3dbdfe|CVE-2026-43284
github fbf68038fee5f4fa53520629|CVE-2026-43284
github e1fc6a165baedbded9e22b6c|CVE-2026-43284
packetstorm bd2236092be59388bfdefee2|CVE-2026-43284
packetstorm 6df9aeddef056b755613be34|CVE-2026-43284
euvd EUVD-2026-28535
packetstorm a48be691052018fbe762d8ea|CVE-2026-43284

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

References