CVE-2026-99285

netfilter: nft_byteorder: remove multi-register support

Description

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.

Key facts

Published
10 Nov 2026
Last changed
10 Nov 2026
Assigned by
Linux
EPSS
0.167% likely to be exploited in the next 30 days, higher than 5.977% of CVEs (scores for 15 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • c301f0981fdd3fd1ffac6836b423c4d7a8e0eb63 up to but excluding 3c5fb3a6c8118d15e60295e76fb5b879021eef43 (affected)
  • c301f0981fdd3fd1ffac6836b423c4d7a8e0eb63 up to but excluding dc29c0478b8564feb9371e715b5a0016eb8903fd (affected)
  • c301f0981fdd3fd1ffac6836b423c4d7a8e0eb63 up to but excluding bb061d3de41707415269be75ebf700efb03ec212 (affected)
  • fca41e5b687e029f69e3a35a2fa31e2560e538dc (affected)
  • 25b42be4e067e107a2559266b54bf07fa5b094fb (affected)
  • 9a865a11d6890d4a789db1eaafebdc8bd092b12c (affected)
  • b8b514b2a6cdfac24911e4910461bcb9db15ca8d (affected)
  • 18a169810cff769a7a697b35058c756805f589e0 (affected)
  • 1a605657adc58b3c8e2c1c66aaa5fecd29072135 (affected)
  • 013deed31ab15ef287b0045e4e7bd8f250e75b94 (affected)
  • 4.19.307 up to but excluding 4.20 (affected)
  • 5.4.269 up to but excluding 5.5 (affected)
  • 5.10.210 up to but excluding 5.11 (affected)
  • 5.15.140 up to but excluding 5.16 (affected)
  • 6.1.64 up to but excluding 6.2 (affected)
  • 6.5.13 up to but excluding 6.6 (affected)
  • 6.6.3 up to but excluding 6.7 (affected)
LinuxLinux
  • Default status: affected
  • 6.7 (affected)
  • 0 up to but excluding 6.7 (unaffected)
  • 6.12.115 up to and including 6.12.* (unaffected)
  • 6.18.59 up to and including 6.18.* (unaffected)
  • 7.1 up to and including * (unaffected)

Timeline

  1. 10 Nov 2026 Published

References