llamaCVEVulnerability Intelligence
/
Linux kernel

CVE-2026-99285

Linux kernel filter bypass in nft_byteorder

An attacker could send packets that get past firewall rules using byte-order conversion across registers.

Parche disponiblenetfilter
Descargar PNG JSON
CVSS
—
N/D
Fuente: —
ExplotaciónSin evidenciaNo figura en CISA KEV
Exploits públicos0Ninguno conocido
Parche7 versiones4.20 · 5.5 · 5.11 · 5.16 …
Exposición8 dDesde la divulgación, 10 nov 2026, 12:37 p. m.
Detección49 minDesde la divulgación hasta su ingreso al índice
Timeline

Ciclo de vida de la vulnerabilidad

Hoy
Divulgación
Publicada
Explotación
Remediación
Monitoreo
Detectada
Verificada
10 nov 26
16 nov 26
19 nov 26
10 nov 26
12 nov 26
14 nov 26
17 nov 26
19 nov 26
FechaFaseEventoDetalle
Divulgación Publicada CVE-2026-99285 divulgada
Monitoreo Detectada Ingresó al índice
Monitoreo Verificada Última verificación contra las fuentes
Resumen

In the Linux kernel, the following vulnerability has been resolved: netfilter: nft_byteorder: remove multi-register support 64bit byteorder conversion is broken when several registers need to be converted because the source register array advances in steps for 4 bytes instead of 8: for (i = ... src64 = nft_reg_load64(&src[i]); ~~~~~ u32 *src nft_reg_store64(&dst64[i], Remove the multi-register support, it has other issues as well: Pablo points out that commit caf3ef7468f7 ("netfilter: nf_tables: prevent OOB access in nft_byteorder_eval") alters semantics: before the loop operated on registers, i.e. for ( ... ) dst32[i] = htons((u16)src32[i]) .. but after the patch it will operate on bytes, which makes this useless to convert e.g. concatenations, which store each compound in its own register. Multi-convert of u32 has one theoretical application: ct mark . meta mark . tcp dport @intervalset Because ct mark and meta mark are host byte order, use with intervals has to convert the byteorder for ct/meta mark value to network byte order (bigendian). nftables emits this: [ meta load mark => reg 1 ] [ byteorder reg 1 = hton(reg 1, 4, 4) ] [ ct load mark => reg 9 ] [ byteorder reg 9 = hton(reg 9, 4, 4) ] ... I.e. two separate calls. Theoretically it could be changed to do: [ meta load mark => reg 1 ] [ ct load mark => reg 9 ] [ byteorder reg 1 = htonl(reg 1, 4, 8) ] ... But then all it would take to change the set to meta mark . tcp dport . ct mark ... and we'd be back to two "byteorder" calls. IOW, support to convert a range of registers is both dysfunctional and dubious. Simplify this: remove the feature. Pablo Neira Ayuso points out that nftables before 1.1.0 can generate incorrect byteorder conversions, see 9fe58952c45a, "evaluate: skip byteorder conversion for selector smaller than 2 bytes" in nftables.git). Affected rulesets fail to load with this change and old userspace due to 'len != size' check.

Versiones

Rangos afectados

Afectada Corregida
Linux≥ 4.19.307 < 4.20
Linux≥ 5.4.269 < 5.5
Linux≥ 5.10.210 < 5.11
Linux≥ 5.15.140 < 5.16
Linux≥ 6.1.64 < 6.2
Linux≥ 6.5.13 < 6.6
Linux≥ 6.6.3 < 6.7
4.19.307
4.20
5.4.269
5.5
5.10.210
5.11
5.15.140
5.16
6.1.64
6.2
6.5.13
6.6
6.6.3
6.7
Remediación

Estado del parche por paquete

Paquete / productoEstadoCorregida enDesde divulgaciónÚltima versión
Linux
Corregida 4.20, 5.5, 5.11, 5.16, 6.2, 6.6, 6.7 — —
Versiones corregidas4.205.55.115.166.26.66.7
Explotación

Arsenal público

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

Referencias
Otrahttps://git.kernel.org/stable/c/3c5fb3a6c8118d15e60295e76fb5b879021eef43
Otrahttps://git.kernel.org/stable/c/dc29c0478b8564feb9371e715b5a0016eb8903fd
Otrahttps://git.kernel.org/stable/c/bb061d3de41707415269be75ebf700efb03ec212

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