CVE-2026-98393
Last modified
CVE-2026-98393 is a vulnerability of currently unknown severity. 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.
Description
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.
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | >= daba287b299ec7a2c61ae3a714920e90e8396ad5, < 83fedc4741210f75be8ca5b487985a242bf6f18d; >= daba287b299ec7a2c61ae3a714920e90e8396ad5, < 81f540827d243b8dad76c1f44e70ea31719f393c; >= daba287b299ec7a2c61ae3a714920e90e8396ad5, < b83641e0ab8b20eefcc4cdc5a059f897375291a2 |
| Linux | Linux | 3.13 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-98393?
How severe is CVE-2026-98393?
How do I fix CVE-2026-98393?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-98387In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98388In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98389In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98390In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98391In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98392In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98394In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98395In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98396In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98397In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98398In the Linux kernel, the following vulnerability has been re…
- CVE-2026-98399In the Linux kernel, the following vulnerability has been re…
Are you affected by CVE-2026-98393?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
