Skip to main content
← All vulnerabilities
CVE-2026-23397

nfnetlink_osf: validate individual option lengths in fingerprints

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
None on Exploit-DB, Metasploit or GitHub

Summary

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.

Timeline

  1. CVE published
  2. Record last updated

Affected versions

  • Linux Linux

    From 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 · fixed in e9cf17b91e733fec725ebcc0b3098bc5ccd505e0; From 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 · fixed in 3c11b5c2436a3a5b450612ab160e3a525b28cfb5; From 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 · fixed in aa0574182c46963c3cdb8cde46ec93aca21100d8; From 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 · fixed in 224f4678812e1a7bc8341bcb666773a0aec5ea6f; From 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 · fixed in ec8bf0571b142f29dc0b68ae2ac3952f7a464b38; From 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 · fixed in 3932620c04c2938c93c0890c225960d3d34ba355; From 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 · fixed in 4c6aa008b913e808c4f4d3cde36cb1d9bb5967c6; From 11eeef41d5f63c7d2f7fdfcc733eb7fb137cc384 · fixed in dbdfaae9609629a9569362e3b8f33d0a20fd783c

  • Linux Linux

    2.6.31

  • KernelLinux

    From 2.6.31 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.167; From 6.2.0 · fixed in 6.6.130; From 6.7.0 · fixed in 6.12.78; From 6.13.0 · fixed in 6.18.20; From 6.19.0 · fixed in 6.19.10

References 8

git.kernel.org