CVE-2026-23397

published 26 Mar 2026 · updated 12 Nov 2026

nfnetlink_osf: validate individual option lengths in fingerprints

7.1HighCVSS 7.1EPSS 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 5.10.253, Kernel 5.15.203, Kernel 6.1.167 and 12 more.

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.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
LinuxKernel>=2.6.31.1 <5.10.253, >=5.11 <5.15.203, >=5.16 <6.1.167, >=6.13 <6.18.20, >=6.19 <6.19.10, >=6.2 <6.6.130, >=6.7 <6.12.78, =2.6.31, =7.0, >=11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 <3932620c04c2938c93c0890c225960d3d34ba355, >=11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 <3c11b5c2436a3a5b450612ab160e3a525b28cfb5, >=11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 <4c6aa008b913e808c4f4d3cde36cb1d9bb5967c6, >=11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 <aa0574182c46963c3cdb8cde46ec93aca21100d8, >=11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 <dbdfaae9609629a9569362e3b8f33d0a20fd783c, >=11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 <e9cf17b91e733fec725ebcc0b3098bc5ccd505e0, >=11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 <ec8bf0571b142f29dc0b68ae2ac3952f7a464b38, >=11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 <224f4678812e1a7bc8341bcb666773a0aec5ea6f5.10.253, 5.15.203, 6.1.167, 6.18.20, 6.19.10, 6.6.130, 6.12.78, 3932620c04c2938c93c0890c225960d3d34ba355, 3c11b5c2436a3a5b450612ab160e3a525b28cfb5, 4c6aa008b913e808c4f4d3cde36cb1d9bb5967c6, aa0574182c46963c3cdb8cde46ec93aca21100d8, dbdfaae9609629a9569362e3b8f33d0a20fd783c, e9cf17b91e733fec725ebcc0b3098bc5ccd505e0, ec8bf0571b142f29dc0b68ae2ac3952f7a464b38, 224f4678812e1a7bc8341bcb666773a0aec5ea6f
linux-kernel: Kernel>=2.6.31 <5.10.253, >=5.11.0 <5.15.203, >=5.16.0 <6.1.167, >=6.13.0 <6.18.20, >=6.19.0 <6.19.10, >=6.2.0 <6.6.130, >=6.7.0 <6.12.785.10.253, 5.15.203, 6.1.167, 6.18.20, 6.19.10, 6.6.130, 6.12.78

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-23397 severity on Zeptric[![CVE-2026-23397](https://zeptric.io/badge/cve/CVE-2026-23397.svg)](https://zeptric.io/cve/CVE-2026-23397)