CVE-2026-98393

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

CVE-2026-98393 is fixed in 20 products on 1 platform, first by DEBIAN-CVE-2026-98393, released October 16, 2026. It is not reported as exploited. Patch Radar priority: Routine.

Routine
CVSS
1.9
Low
Exploitation
None reported
No vendor assessment
CISA KEV
Not listed
Not in the Known Exploited Vulnerabilities catalog
EPSS
0.0020
10th percentile

In the Linux kernel, the following vulnerability has been resolved: net: ipv4: Fix UDP length overflow with PMTU discover and big MTU This commit bounds cork->base.fragsize to IP_MAX_MTU to avoid a possible overflow of UDP length that triggers a WARN in udp_set_len_short when setsockopt IP_MTU_DISCOVER is set to IP_PMTUDISC_PROBE, and a large packet is sent over a netdev with an unusually large MTU. Steps to reproduce: 1. Set device MTU bigger than IP_MAX_MTU + 20. cork->base.fragsize will be set to that MTU in ip_setup_cork. 2. Set IP_MTU_DISCOVER to IP_PMTUDISC_PROBE. It lets maxnonfragsize be set to device MTU (cork->fragsize) in __ip_append_data, rather than to IP_MAX_MTU. 3. Send 65528 bytes of payload (+8 bytes of UDP header, +20 bytes of IPv4 header). Device MTU allows it (it's only one byte bigger than IP_MAX_MTU + IPv4 header, 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. Note: IP_PMTUDISC_DO with IPv4 is safe, because ip_dst_mtu_maybe_forward always clamps at IP_MAX_MTU, unlike ip6_dst_mtu_maybe_forward. The Fixes tag points at the first commit where I could reproduce the overflow with IPv4 and IP_PMTUDISC_PROBE.

Where it's fixed

ProductFixed inFixReleased
Linux
bpftool6.18 · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
bpftool6.18-debuginfo · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel-livepatch-6.18.54-121.166 · amzn 2023 1:1.0-0.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18 · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-debuginfo · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-debuginfo-common-aarch64 · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-debuginfo-common-x86_64 · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-devel · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-headers · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-modules-extra · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-modules-extra-common · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-tools · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-tools-debuginfo · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
kernel6.18-tools-devel · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
linux · Debian 14 7.2.7-1 DEBIAN-CVE-2026-98393 Oct 16, 2026
microvm-kernel6.18 · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
perf6.18 · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
perf6.18-debuginfo · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
python3-perf6.18 · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026
python3-perf6.18-debuginfo · amzn 2023 1:6.18.54-121.166.amzn2023 ALAS2023-2026-3192 Nov 7, 2026

Patch Radar data is free to use with attribution. Terms and how to credit it.

Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.