← voltar
CVE-2026-43284

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

CVSS 8.8 HIGHEPSS 93.4%CWE-123
Em resumo

Uma falha no kernel do Linux permite que dados criptografados em ESP (protocolo de segurança) sejam descriptografados diretamente na memória compartilhada ao usar UDP com MSG_SPLICE_PAGES, expondo potencialmente o conteúdo dos pacotes.

Detalhe técnico

O caminho de entrada ESP no kernel Linux não marca fragmentos compartilhados de skb com SKBFL_SHARED_FRAG quando datagramas UDP fazem splice de páginas de pipes, permitindo descriptografia in-place sobre memória não privada. O caminho rápido sem COW assume propriedade exclusiva de skbs não-clonados, mas páginas compartilhadas de pipes violam essa suposição. A correção requer definir a flag de fragmento compartilhado para operações UDP splice e retroceder para skb_cow_data() na entrada ESP quando a flag está presente.

Resumo gerado e traduzido por IA a partir da descrição oficial.
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:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Produtos afetados
Linux · Linux
PoCs públicas encontradas29
githubgithub.com/linnemanlabs/dirtyfrag-arm6426githubgithub.com/0xBlackash/CVE-2026-4328414githubgithub.com/liamromanis101/DirtyFrag-Detector13githubgithub.com/Percivalll/Dirty-Frag-Kubernetes-PoC12githubgithub.com/haydenjames/dirty-frag-check7githubgithub.com/mym0us3r/DIRTY-FRAG-Detection-with-Wazuh-4.14.43githubgithub.com/AK777177/Dirty-Frag-Analysis2githubgithub.com/LucasPDiniz/CVE-2026-432841githubgithub.com/kuniyal08/Dirty-Frag-CVE-2026-432841githubgithub.com/ChernStepanov/DirtyFrag-for-dummies0githubgithub.com/xd20111/CVE-2026-432840githubgithub.com/grabesec/XCP_ng_CVE-2026-43284_tester0githubgithub.com/Koshmare-Blossom/DirtyFrag-go0githubgithub.com/DylanClaudio/Reporte-de-Escalada-de-Privilegios-Local-Dirty-Frag0githubgithub.com/AtlasVector/Dirty-Frag-CVE-2026-432840githubgithub.com/1neptune/DirtyFrag0githubgithub.com/g0thamRabb1t/dirtyfrag-cve-2026-43284-auditd-detection0githubgithub.com/t1ckprivate/CVE-2026-43284-Dirty-Frag0githubgithub.com/scriptzteam/Paranoid-Dirty-Frag-CVE-2026-432840githubgithub.com/suominen/CVE-2026-432840githubgithub.com/metalx1993/dirtyfrag-patches0githubgithub.com/ryan2929/CVE-2026-43284-0githubgithub.com/gagaltotal/CVE-2026-43284-CVE-2026-43500-scan0githubgithub.com/Aiyakami/rust_dirtyfrag0githubgithub.com/XRSecCD/202605_dirty_frag0githubgithub.com/FrosterDL/CVE-2026-432840exploitdbwww.exploit-db.com/exploits/52585não verificadoexploitdbwww.exploit-db.com/exploits/52591não verificadocve_referencegithub.com/V4bel/dirtyfragnão verificado
⚠ Recursos públicos, para você avaliar a exposição de sistemas que controla ou está autorizado a testar. Teste apenas com autorização.

Quer saber se a sua infraestrutura está exposta a isto?

Falar com a TrueHacking →