PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-80793 Linux CVE debrief

A vulnerability in the Linux kernel's IPv4 fragmentation handling can cause a softlockup when processing packets with undersized MTUs. The issue arises from ip_do_fragment() not rejecting MTUs smaller than the IPv4 header length plus 8 bytes, leading to a fragmentation state that fails to make forward progress. This can be triggered by routing packets to a device with an MTU of 20 or by using 'mtu lock 20' in a route. The fix involves rejecting such undersized MTUs with an -EMSGSIZE error.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-09-04
Original CVE updated
2026-10-19
Advisory published
2026-09-04
Advisory updated
2026-10-19

Who should care

Defenders responsible for Linux kernel infrastructure, network administrators managing IPv4 traffic, and security teams handling vulnerability remediation should assess exposure and prioritize patching.

Why it matters

This vulnerability in the Linux kernel's IPv4 fragmentation handling can lead to a denial-of-service condition. Defenders should prioritize patching affected systems, particularly those handling IPv4 traffic with restrictive MTU configurations. The vulnerability's impact is limited to specific scenarios and does not allow for arbitrary code execution or data theft.

  • Potential for denial-of-service due to softlockup
  • Need for verification of Linux kernel versions and MTU configurations
  • Possible impact on network performance and stability

Technical summary

The Linux kernel's IPv4 fragmentation handling does not properly reject undersized MTUs, leading to a potential softlockup. ip_do_fragment() subtracts the IPv4 header length from the effective MTU and passes the result to ip_frag_next(). If the effective MTU is smaller than the IPv4 header length plus 8, ip_frag_next() can round the fragment payload length down to zero, causing the fragmentation state to stall.

Defensive priority

Defenders should prioritize verifying and applying patches for Linux kernel versions affected by this vulnerability, particularly for systems handling IPv4 traffic with potentially restrictive MTU configurations.

Recommended defensive actions

  • Verify and apply Linux kernel patches for this vulnerability
  • Review and adjust MTU configurations for IPv4 traffic
  • Monitor for unusual traffic patterns that could indicate exploitation attempts
  • Perform an inventory of assets using the Linux kernel
  • Review system logs for indicators of potential exploitation
  • Implement compensating controls for exposed systems
  • Track remediation progress and verify patch deployment

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description and potential impact. However, specific exploitation details or affected versions beyond the Linux kernel are not provided, requiring verification from official Linux kernel sources.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-80793 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-80793

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-80793 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-80793

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/3556beb8ca86677af2aca5bfbed6f8e790fccc83

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/36e0741833bd823866f8cb9f112f37cea1a70b60

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/515b6816ba0c12d8415c88e5f41e6ec029e35cfa

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/74ce7389f8f562d39015f59a00ef7ad6acd37803

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/a716a64a4ba68cd46f2745fba2b1099fe8e0aa59

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/b0ea911453ce7210e8200a07a94d2458bd1e6430

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/c0726f0caf8c6b3208552949e17d23634a2f3129

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/c8a74adccaf028223054633b532593101dfcc581

    416baaa9-dc9f-4396-8d5f-8c081fb06d67

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.