cve.bz

CVE-2026-98393 linux linux

no score yetEPSS 0.2%Fix available

linux linux: no CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.
EPSS
0.2% (unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-98393 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-98393?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-98393?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-98393 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-98393

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-98393](https://cve.bz/cve/badge/CVE-2026-98393.svg)](https://cve.bz/cve/CVE-2026-98393)

HTML:

<a href="https://cve.bz/cve/CVE-2026-98393"><img src="https://cve.bz/cve/badge/CVE-2026-98393.svg" alt="CVE-2026-98393"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Linux3.13 and later

Fixed in

ProductRelease lineFixed in
Linux6.186.18.53
Linux7.27.2.7
Linuxlater releases7.3

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13linuxno fix listedDEBIAN-CVE-2026-98393
Debian14linux7.2.7-1DEBIAN-CVE-2026-98393
Ubuntu16.04:LTSlinux-hwe-edgeno fix listedUBUNTU-CVE-2026-98393
Ubuntu18.04:LTSlinux-gcp, linux-hwe, linux-oem and 12 moreno fix listedUBUNTU-CVE-2026-98393
Ubuntu20.04:LTSlinux-gke, linux-gkeop, linux-riscv and 26 moreno fix listedUBUNTU-CVE-2026-98393
Ubuntu22.04:LTSlinux, linux-aws, linux-gcp and 57 moreno fix listedUBUNTU-CVE-2026-98393
Ubuntu24.04:LTSlinux, linux-aws, linux-gcp and 44 moreno fix listedUBUNTU-CVE-2026-98393
Ubuntu24.04:LTSlinux-aws-7.07.0.0-1017.18~24.04.1UBUNTU-CVE-2026-98393 USN-9020-1
Ubuntu24.04:LTSlinux-azure-fde-7.07.0.0-1019.19~24.04.1UBUNTU-CVE-2026-98393 USN-9020-1
Ubuntu24.04:LTSlinux-gcp-7.07.0.0-1017.19~24.04.1UBUNTU-CVE-2026-98393 USN-9020-1
Ubuntu24.04:LTSlinux-hwe-7.07.0.0-42.42~24.04.1UBUNTU-CVE-2026-98393 USN-8959-1
Ubuntu24.04:LTSlinux-oracle-7.07.0.0-1016.18~24.04.1UBUNTU-CVE-2026-98393 USN-9020-1
Ubuntu24.04:LTSlinux-riscv-7.07.0.0-42.42.1~24.04.1UBUNTU-CVE-2026-98393
Ubuntu26.04:LTSlinux7.0.0-42.42UBUNTU-CVE-2026-98393 USN-8959-1
20 more for Ubuntu in the JSON and on Ubuntu's page.
Azure Linux3kernelno fix listedAZL-108105
Alpaquita23, 25linux-ltsno fix listedBELL-CVE-2026-98393
Alpaquitastreamlinux-lts6.18.53-r0BELL-CVE-2026-98393

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Alpaquita.

Red Hat

Red Hat rates this Low.

Red Hat's statement

A flaw of low impact was found in the Linux kernel IPv4 networking stack. It affects the kernel and kernel-rt packages across Red Hat Enterprise Linux 7, 8, 9, and 10 update streams, as well as the kernel components shipped in Red Hat OpenShift Container Platform (RHEL CoreOS) and Red Hat In-Vehicle OS. A local user can trigger an integer overflow in the UDP transmit path by setting the IP_MTU_DISCOVER socket option to IP_PMTUDISC_PROBE and sending a large UDP payload over a network device configured with an unusually large MTU (greater than IP_MAX_MTU + 20). The computed UDP length can then reach 65536, overflowing the 16-bit UDP length field and triggering a kernel WARN in udp_set_len_short, potentially causing a local denial of service; systems configured with panic_on_warn may panic as a result of the warning. Confidentiality and integrity are not affected, and no privilege escalation primitive is supported by the affected code path. Red Hat rates this flaw as low severity because exploitation requires local access combined with an uncommon network device configuration, and the demonstrated impact is a kernel warning and failure of the oversized packet to be delivered. Because of the low severity and the unusual configuration required to trigger the issue, the fix is currently deferred for the affected Red Hat products; the residual risk is a local denial of service limited to systems that use oversized device MTUs together with IP_PMTUDISC_PROBE. IPv4 with IP_PMTUDISC_DO is not affected because the path MTU is always clamped at IP_MAX_MTU in that mode. Red Hat Enterprise Linux 6 is out of support and is not scheduled to receive a fix.

Red Hat's mitigation

This issue can only be triggered on network devices configured with an MTU larger than IP_MAX_MTU (65535 bytes) while an application uses the IP_PMTUDISC_PROBE Path MTU discovery socket option. As a workaround, do not configure network interfaces with MTU values above 65535 bytes (for example, keep interfaces at standard values such as 1500); with such configurations the UDP length cannot overflow the 16-bit length field.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10kernelFix deferred
Red Hat Enterprise Linux 6kernelOut of support scope
Red Hat Enterprise Linux 7kernelFix deferred
Red Hat Enterprise Linux 7kernel-rtFix deferred
Red Hat Enterprise Linux 8kernelFix deferred
Red Hat Enterprise Linux 8kernel-rtFix deferred
Red Hat Enterprise Linux 9kernelFix deferred
Red Hat Enterprise Linux 9kernel-rtFix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-8Fix deferred
Red Hat OpenShift Container Platform 4openshift/ose-rhel-coreos-9Fix deferred
Red Hat OpenShift Container Platform 5openshift/ose-rhel-coreos-9Fix deferred

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-98393.

References

Check your stackJSON