CVE-2026-97984

net: ipv6: Fix UDP length overflow with PMTU discover and big MTU

Description

In the Linux kernel, the following vulnerability has been resolved: net: ipv6: Fix UDP length overflow with PMTU discover and big MTU This commit bounds cork->base.fragsize to IP6_MAX_MTU for UDP sockets to avoid a possible overflow of UDP length that triggers a WARN in udp_set_len_short when setsockopt IPV6_MTU_DISCOVER is set to IPV6_PMTUDISC_DO or IPV6_PMTUDISC_PROBE, and a large packet is sent over a netdev with an unusually large MTU. Steps to reproduce (included in the new selftest): 1. Set device MTU bigger than IP6_MAX_MTU. cork->base.fragsize will be set to that MTU in ip6_setup_cork. 2. Set IPV6_MTU_DISCOVER to IPV6_PMTUDISC_PROBE or IPV6_PMTUDISC_DO. It lets maxnonfragsize be set to device MTU (cork->fragsize) in __ip6_append_data, rather than to IP6_MAX_MTU. 3. Send 65528 bytes of payload (+8 bytes of UDP header, +40 bytes of IPv6 header). Device MTU allows it (it's only one byte bigger than IP6_MAX_MTU, and the device MTU is bigger than that). 4. The UDP length in the built packet is 65536, which overflows the 16-bit length field and triggers the WARN in udp_set_len_short. To avoid breaking sending UDP jumbograms over raw IPv6 sockets, limit the change to UDP sockets only. The original overflow bug with IPv6 and IPV6_PMTUDISC_DO seems to predate git history (verified reproduction on 2.6.21), was fixed later, and then reappeared in commit 427faee167bc ("net: ipv6: introduce ip6_dst_mtu_maybe_forward"), which is chosen as the Fixes tag here. The overflow with IPV6_PMTUDISC_PROBE reproduces since its introduction in commit 628a5c561890 ("[INET]: Add IP(V6)_PMTUDISC_RPOBE").

Key facts

Published
25 Sep 2026
Last changed
19 Oct 2026
Assigned by
Linux
EPSS
0.168% likely to be exploited in the next 30 days, higher than 6.149% of CVEs (scores for 17 Nov 2026)

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
LinuxLinux
  • Default status: unaffected
  • 427faee167bce4ccb0b22f6815a9ac509e31d4c3 up to but excluding 1dd562f3019019ffdf4b396570613053facda9ee (affected)
  • 427faee167bce4ccb0b22f6815a9ac509e31d4c3 up to but excluding 1d56a00ec91f2885c64ea5b8cea18cb746b91bbb (affected)
  • 427faee167bce4ccb0b22f6815a9ac509e31d4c3 up to but excluding ce66352d3eb21825410af8b91db7cc4bb8e22c98 (affected)
  • 427faee167bce4ccb0b22f6815a9ac509e31d4c3 up to but excluding e01b7c176d9af2b7c22bb3fe12cf9a7904f99fdc (affected)
  • 427faee167bce4ccb0b22f6815a9ac509e31d4c3 up to but excluding 0ae10b6be49b425827659b23bcce498f80eb7182 (affected)
LinuxLinux
  • Default status: affected
  • 5.15 (affected)
  • 0 up to but excluding 5.15 (unaffected)
  • 6.6.158 up to and including 6.6.* (unaffected)
  • 6.12.111 up to and including 6.12.* (unaffected)
  • 6.18.53 up to and including 6.18.* (unaffected)
  • 7.2.7 up to and including 7.2.* (unaffected)
  • 7.3 up to and including * (unaffected)

Timeline

  1. 25 Sep 2026 Published

References