CVE-2026-99285

published 10 Nov 2026 · updated 20 Nov 2026

netfilter: nft_byteorder: remove multi-register support

5.0MediumEPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Kernel dc29c0478b8564feb9371e715b5a0016eb8903fd, Kernel 4.20, Kernel 5.11 and 9 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=c301f0981fdd3fd1ffac6836b423c4d7a8e0eb63 <dc29c0478b8564feb9371e715b5a0016eb8903fd, >=4.19.307 <4.20, >=5.10.210 <5.11, >=5.15.140 <5.16, >=5.4.269 <5.5, >=6.1.64 <6.2, >=6.5.13 <6.6, >=6.6.3 <6.7, >=c301f0981fdd3fd1ffac6836b423c4d7a8e0eb63 <3c5fb3a6c8118d15e60295e76fb5b879021eef43, >=c301f0981fdd3fd1ffac6836b423c4d7a8e0eb63 <bb061d3de41707415269be75ebf700efb03ec212, =013deed31ab15ef287b0045e4e7bd8f250e75b94, =18a169810cff769a7a697b35058c756805f589e0, =1a605657adc58b3c8e2c1c66aaa5fecd29072135, =25b42be4e067e107a2559266b54bf07fa5b094fb, =6.7, =9a865a11d6890d4a789db1eaafebdc8bd092b12c, =b8b514b2a6cdfac24911e4910461bcb9db15ca8d, =fca41e5b687e029f69e3a35a2fa31e2560e538dcdc29c0478b8564feb9371e715b5a0016eb8903fd, 4.20, 5.11, 5.16, 5.5, 6.2, 6.6, 6.7, 3c5fb3a6c8118d15e60295e76fb5b879021eef43, bb061d3de41707415269be75ebf700efb03ec212
linux-kernel: Kernel>=5.10.210 <5.11, >=5.15.140 <5.16, >=5.4.269 <5.5, >=6.1.64 <6.2, >=6.13.0 <6.18.59, >=6.5.13 <6.6, >=6.6.3 <6.7, >=6.7.0 <6.12.115, >=4.19.307 <4.205.11, 5.16, 5.5, 6.2, 6.18.59, 6.6, 6.7, 6.12.115, 4.20

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in Kernel, strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-99285 severity on Zeptric[![CVE-2026-99285](https://zeptric.io/badge/cve/CVE-2026-99285.svg)](https://zeptric.io/cve/CVE-2026-99285)