CVE-2026-99285
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.
Timeline
- 2026-11-10Published by the CNA17:37 UTC
Affected products
Products listed as vulnerable. Upgrade to the version under "Fixed in", or a later one.
| Product | Vulnerable versions | Fixed in |
|---|---|---|
| linux linux | from 4.19.307 before 4.20fixed in 4.20from 5.10.210 before 5.11fixed in 5.11from 5.15.140 before 5.16fixed in 5.16from 5.4.269 before 5.5fixed in 5.5from 6.1.64 before 6.2fixed in 6.2(+2 more) | 4.205.115.165.56.2 |
| linux linux_kernel | from 6.7 before 6.12.115fixed in 6.12.115from 6.7 before 6.18.59fixed in 6.18.59from 6.7 before 7.1fixed in 7.1from 4.19.307no fix listedfrom 5.10.210no fix listed(+5 more) | 6.12.1156.18.597.1not listednot listed |
References
- https://git.kernel.org/stable/c/3c5fb3a6c8118d15e60295e76fb5b879021eef43
- https://git.kernel.org/stable/c/bb061d3de41707415269be75ebf700efb03ec212
- https://git.kernel.org/stable/c/dc29c0478b8564feb9371e715b5a0016eb8903fd
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cve_lookup/CVE-2026-99285'curl 'https://api.contrastcyber.com/cve_risk_score/CVE-2026-99285'curl 'https://api.contrastcyber.com/cve_exploit/CVE-2026-99285'curl 'https://api.contrastcyber.com/cve_products/CVE-2026-99285'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- OWASP Top 10 categories by the OWASP Foundation (CC BY 3.0).
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).