Quick answers
- Is CVE-2026-99285 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-99285 being exploited in the wild.
- How severe is CVE-2026-99285?
- Informational severity, published 10 November 2026.
- Which products and versions are affected?
- Unknown Linux kernel <UNKNOWN>.
- Is there a fix for CVE-2026-99285?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-99285 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-99285?
- Check whether you run Unknown Linux kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The nft_byteorder module incorrectly handles multi-register 64-bit byteorder conversion due to stepping by 4 bytes instead of 8 bytes through the source register array, causing out-of-bounds access and semantic breakage in byte order transformations. The vulnerability affects network packet filtering rules (nftables) that perform byteorder conversions across multiple registers, particularly in concatenated field rules. A fix removes the broken multi-register support entirely, requiring userspace nftables before version 1.1.0 to be upgraded to avoid rule loading failures.
Affected products
- <UNKNOWN> Linux kernel <UNKNOWN>
Timeline
- 2026-11-10: disclosed