llamaCVEVulnerability Intelligence
/
Linux kernel

CVE-2026-53362

Linux kernel memory corruption in IPv6 UDP send path

A local user can corrupt memory via IPv6 UDP packets, crashing the system or escalating privileges.

Texto original en inglés · Ver en español

CISA KEV · explotación activaCrítica · en CISA KEVParche disponibleipv6
Descargar PNG JSON
CVSS 3.1
7.8
Alta
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Fuente: CNA
ExplotaciónActivaEn CISA KEV desde 27 ago 2026
Exploits públicos0Explotada, pero sin código público enlazado
Parche5 versiones6.1.177 · 6.6.144 · 6.12.95 · 6.18.38 …
Exposición140 dDesde la divulgación, 4 jul 2026, 6:56 a. m.
Detección110 dDesde la divulgación hasta su ingreso al índice
Decisión SSVCAtender
Priorizar en el próximo ciclo de cambios
Explotación activa (CISA KEV), no automatizable e impacto técnico total. Plazo KEV: 30 ago 2026.
CVSS alto, corazón bajito. Priorízala.Pide la ventana de mantenimiento antes del viernes.
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Evaluación SSVC
Modificada
Explotación
CISA KEV
Remediación
Plazo KEV
Monitoreo
Detectada
Fuente: OSV
Verificada
4 jul 26
27 ago 26
28 ago 26
30 ago 26
15 oct 26
22 oct 26
24 oct 26
19 nov 26
21 nov 26
4 jul 26
8 ago 26
12 sept 26
17 oct 26
21 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-53362 divulgada · CVSS 7.8 (CNA)
Explotación CISA KEV Agregada al catálogo de vulnerabilidades explotadas
Divulgación Evaluación SSVC CISA-ADP · explotación activa
Remediación Plazo KEV Fecha límite de remediación para agencias federales (EE. UU.)
Divulgación Modificada Última actualización del registro
Monitoreo Detectada Ingresó al índice
Monitoreo Fuente: OSV Registro visto por primera vez en OSV
Monitoreo Verificada Última verificación contra las fuentes
Resumen
Resumen generado por IA · CC-BY 4.0 · 18 nov 2026

A flaw in the Linux kernel's IPv6 networking code can corrupt kernel memory by copying data past the end of a socket buffer. A local attacker with a low-privilege account can trigger it, with no user interaction, by sending UDPv6 data using the MSG_MORE and MSG_SPLICE_PAGES flags together. It is listed as exploited in attacks.

Affects Linux kernels from 6.0 onward up to the fixed releases, when a UDPv6 socket sends with MSG_MORE and MSG_SPLICE_PAGES on the paged allocation path. Fixed in 6.1.177, 6.6.144, 6.12.95, 6.18.38 and 7.1.3.

¿Qué significa?In the IPv6 send path, the kernel does not account for leftover data (fraggap) from a previous packet buffer when it uses paged allocation. The copy can then write past the end of the socket buffer into the trailing skb_shared_info structure, corrupting kernel memory.
¿Quién está afectado?The advisory lists Linux kernel ranges 6.0.0 up to 6.1.177, 6.2.0 up to 6.6.144, 6.7.0 up to 6.12.95, 6.13.0 up to 6.18.38 and 6.19.0 up to 7.1.3. The bug needs the paged-allocation branch of __ip6_append_data() (MSG_MORE, NETIF_F_SG or large fraglen) on a UDPv6 socket sending with MSG_MORE and MSG_SPLICE_PAGES, on a packet that is not the first one. Running `uname -r` shows the kernel version in use.
¿Qué hacer?Upgrade to a kernel containing the fix: 6.1.177, 6.6.144, 6.12.95, 6.18.38 or 7.1.3, depending on the kernel series in use. The facts give no workaround.
Descripción original del registro

In the Linux kernel, the following vulnerability has been resolved: ipv6: account for fraggap on the paged allocation path In __ip6_append_data(), when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen), alloclen and pagedlen are computed as alloclen = fragheaderlen + transhdrlen; pagedlen = datalen - transhdrlen; datalen already includes fraggap (datalen = length + fraggap). When fraggap is non-zero, this is not the first skb and transhdrlen is zero. The fraggap bytes carried over from the previous skb are copied just past the fragment headers in the new skb's linear area. The linear area is therefore undersized by fraggap bytes while pagedlen is overstated by the same amount, and the copy writes past skb->end into the trailing skb_shared_info. An unprivileged user can trigger this via a UDPv6 socket using MSG_MORE together with MSG_SPLICE_PAGES. The bad accounting was introduced by commit 773ba4fe9104 ("ipv6: avoid partial copy for zc"). Before commit ce650a166335 ("udp6: Fix __ip6_append_data()'s handling of MSG_SPLICE_PAGES"), the negative copy value caused -EINVAL to be returned. That later commit allowed MSG_SPLICE_PAGES to proceed in this case, making the corruption triggerable. The non-paged branch sets alloclen to fraglen, which already accounts for fraggap because datalen does. Bring the paged branch in line by adding fraggap to alloclen and subtracting it from pagedlen. After this adjustment, copy no longer collapses to -fraggap on the paged path, so remove the stale comment describing that old arithmetic. Since a negative copy is no longer expected for a valid MSG_SPLICE_PAGES case, remove the MSG_SPLICE_PAGES exception from the negative copy check.

Contexto

Condiciones y alcance

Condiciones necesarias para que el fallo sea explotable
01
The paged-allocation branch of __ip6_append_data() is taken (MSG_MORE, NETIF_F_SG or large fraglen)“when the paged-allocation branch is taken (MSG_MORE / NETIF_F_SG / large fraglen)”
02
A UDPv6 socket sends with MSG_MORE together with MSG_SPLICE_PAGES“An unprivileged user can trigger this via a UDPv6 socket using MSG_MORE together with MSG_SPLICE_PAGES.”
03
The skb is not the first one, so fraggap is non-zero“When fraggap is non-zero, this is not the first skb and transhdrlen is zero.”
¿Quién debe revisar?Teams running Linux kernels with IPv6 UDP, where local unprivileged users can send with MSG_MORE and MSG_SPLICE_PAGES.
Vector CVSS 3.1

Desglose de métricas

Opción resaltada = valor del vector · izquierda = peor caso · CNA
Vector de ataqueAV:L
RedAdyacenteLocalFísica
ComplejidadAC:L
BajaAlta
PrivilegiosPR:L
NingunoBajosAltos
InteracciónUI:N
NingunaRequerida
AlcanceS:U
CambiadoSin cambio
ConfidencialidadC:H
AltoBajoNinguno
IntegridadI:H
AltoBajoNinguno
DisponibilidadA:H
AltoBajoNinguno
Score de explotaciónQué tan fácil y probable es que la exploten
10.0/ 10Muy alto
Vector 6.4 (fácil) · +3.6 por explotación activa.
Versiones

Rangos afectados

Afectada Corregida
Linux≥ 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 14200d435af9a9eeb444f529fc2f689a236b7962
Linux≥ 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 46f201f8b4c39633a1fa3dc12459f506d470993d
Linux≥ 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 6374fb9edf72c67a118a2c214a0dddd04c921e0a
Linux≥ 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 65fb14cbebb0cd0eff903a22d33537ddc8b95769
Linux≥ 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < 736b380e28d0480c7bc3e022f1950f31fe53a7c5
Linux≥ 773ba4fe9104a64a54d1c00f0fb6ffb95def2b03 < e9eacf19281ea2498b36291b56c9606118c2d74e
Kernel≥ 6.0.0 < 6.1.177
Kernel≥ 6.2.0 < 6.6.144
Kernel≥ 6.7.0 < 6.12.95
Kernel≥ 6.13.0 < 6.18.38
Kernel≥ 6.19.0 < 7.1.3
14200d435af9a9eeb444f529fc2f689a236b7962
e9eacf19281ea2498b36291b56c9606118c2d74e
6.6.144
6.12.95
6.18.38
7.1.3
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Linux
Corregida 6.1.177, 6.6.144, 6.12.95, 6.18.38, 7.1.3 — —
Versiones corregidas6.1.1776.6.1446.12.956.18.387.1.3
Explotación

Arsenal público

Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.

Referencias
Fabricantehttps://git.kernel.org/stable/c/14200d435af9a9eeb444f529fc2f689a236b7962
Fabricantehttps://git.kernel.org/stable/c/65fb14cbebb0cd0eff903a22d33537ddc8b95769
Fabricantehttps://git.kernel.org/stable/c/46f201f8b4c39633a1fa3dc12459f506d470993d
Fabricantehttps://git.kernel.org/stable/c/6374fb9edf72c67a118a2c214a0dddd04c921e0a
Fabricantehttps://git.kernel.org/stable/c/e9eacf19281ea2498b36291b56c9606118c2d74e
Fabricantehttps://git.kernel.org/stable/c/736b380e28d0480c7bc3e022f1950f31fe53a7c5

Las referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.