CVE-2026-23397
In the Linux kernel, the following vulnerability has been resolved: …
In the Linux kernel, the following vulnerability has been resolved: nfnetlink_osf: validate individual option lengths in fingerprints nfnl_osf_add_callback() validates opt_num bounds and string NUL-termination but does not check individual option length fields. A zero-length option causes nf_osf_match_one() to enter the option matching loop even when foptsize sums to zero, which matches packets with no TCP options where ctx->optp is NULL: Oops: general protection fault KASAN: null-ptr-deref in range [0x0000000000000000-0x0000000000000007] RIP: 0010:nf_osf_match_one (net/netfilter/nfnetlink_osf.c:98) Call Trace: nf_osf_match (net/netfilter/nfnetlink_osf.c:227) xt_osf_match_packet (net/netfilter/xt_osf.c:32) ipt_do_table (net/ipv4/netfilter/ip_tables.c:293) nf_hook_slow (net/netfilter/core.c:623) ip_local_deliver (net/ipv4/ip_input.c:262) ip_rcv (net/ipv4/ip_input.c:573) Additionally, an MSS option (kind=2) with length < 4 causes out-of-bounds reads when nf_osf_match_one() unconditionally accesses optp[2] and optp[3] for MSS value extraction. While RFC 9293 section 3.2 specifies that the MSS option is always exactly 4 bytes (Kind=2, Length=4), the check uses "< 4" rather than "!= 4" because lengths greater than 4 do not cause memory safety issues -- the buffer is guaranteed to be at least foptsize bytes by the ctx->optsize == foptsize check. Reject fingerprints where any option has zero length, or where an MSS option has length less than 4, at add time rather than trusting these values in the packet matching hot path.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- git.kernel.org/stable/c/224f4678812e1a7bc8341bcb666773a0aec5ea6f
- git.kernel.org/stable/c/3932620c04c2938c93c0890c225960d3d34ba355
- git.kernel.org/stable/c/4c6aa008b913e808c4f4d3cde36cb1d9bb5967c6
- git.kernel.org/stable/c/aa0574182c46963c3cdb8cde46ec93aca21100d8
- git.kernel.org/stable/c/dbdfaae9609629a9569362e3b8f33d0a20fd783c
- git.kernel.org/stable/c/ec8bf0571b142f29dc0b68ae2ac3952f7a464b38
- git.kernel.org/stable/c/3c11b5c2436a3a5b450612ab160e3a525b28cfb5
- git.kernel.org/stable/c/e9cf17b91e733fec725ebcc0b3098bc5ccd505e0
- nvd.nist.gov/vuln/detail/CVE-2026-23397
- cve.org/CVERecord?id=CVE-2026-23397
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.