CVE-2026-43500
In the Linux kernel, the following vulnerability has been resolved: rxrpc: Also unshare DATA/RESPONSE packets when paged frags are present The DATA-packet handler in rxrpc_input_call_event() and the RESPONSE handler in rxrpc_verify_response() copy the skb to a linear one before calling into the security ops only when skb_cloned() is true. An skb that is not cloned but still carries externally-owned paged fragments (e.g. SKBFL_SHARED_FRAG set by splice() into a UDP socket via __ip_append_data, or a chained skb_has_frag_list()) falls through to the in-place decryption path, which binds the frag pages directly into the AEAD/skcipher SGL via skb_to_sgvec(). Extend the gate to also unshare when skb_has_frag_list() or skb_has_shared_frag() is true. This catches the splice-loopback vector and other externally-shared frag sources while preserving the zero-copy fast path for skbs whose frags are kernel-private (e.g. NIC page_pool RX, GRO). The OOM/trace handling already in place is reused.
- Published May 11, 2026
- CVSS 7.8 high
- 2.3% chance of exploitation in the next 30 days (EPSS)
- A Metasploit module exploits it
- A fix is available
Affected software
In the news
- Exploits and vulnerabilities in Q2 2026 Securelist ·
- Copy Fail and Its Descendants: A Real Human's Guide to Kernel Page-Cache LPEs VulnCheck Blog ·
- Ongoing updates on Copy.fail and variants AWS Security Bulletins ·
- Dirty Frag and other issues in Amazon Linux kernels AWS Security Bulletins ·
- Networking subsystem Privilege Escalation - Linux Kernel - "Dirty Frag" Red Hat Security Bulletins ·