PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-74543 Linux CVE debrief

A memory leak vulnerability was found in the Linux kernel's UDP tunnel NIC offload code. When device registration fails, the code returns early without freeing the allocated struct udp_tunnel_nic, leading to a permanent memory leak. The fix involves removing the early return and synchronously canceling any pending work with cancel_delayed_work_sync() before freeing the struct.

Vendor
Linux
Product
Unknown
CVSS
Unknown
CISA KEV
Not listed in stored evidence
Original CVE published
2026-08-15
Original CVE updated
2026-10-30
Advisory published
2026-08-15
Advisory updated
2026-10-30

Who should care

Linux kernel developers, administrators who manage Linux-based systems, and security teams responsible for vulnerability management and patch application. These stakeholders should review and apply the patch to fix the memory leak vulnerability and monitor systems for potential memory leaks.

Why it matters

A memory leak vulnerability was found in the Linux kernel's UDP tunnel NIC offload code. The vulnerability can lead to potential denial-of-service (DoS) attacks if exploited. Linux kernel developers and administrators who manage Linux-based systems should review and apply the patch to fix the vulnerability.

  • Memory leak vulnerability can lead to potential denial-of-service (DoS) attacks
  • Exploitation of this vulnerability requires authentication and access to the system
  • Verification of patch application and system monitoring are necessary to prevent exploitation

Technical summary

The vulnerability is caused by an early return in udp_tunnel_nic_unregister() when device registration fails. This leads to a memory leak of the struct udp_tunnel_nic allocated in udp_tunnel_nic_alloc(). The fix involves removing the early return and synchronously canceling any pending work with cancel_delayed_work_sync() before freeing the struct. This change prevents permanent memory leaks in the Linux kernel's UDP tunnel NIC offload code. Linux kernel developers and administrators should review and apply the patch.

Defensive priority

Medium

Recommended defensive actions

  • Review and apply the patch to fix the memory leak vulnerability
  • Update Linux kernel to the latest version
  • Monitor system for potential memory leaks
  • Perform vulnerability assessment to identify potential exposure
  • Implement compensating controls for exposed systems
  • Track exceptions and retest remediated assets
  • Review relevant monitoring, detection, and logs for exposed assets

Evidence notes

The vulnerability was reported by syzbot and fixed by removing the early return in udp_tunnel_nic_unregister(). The fix also involves switching udp_tunnel_nic_device_sync_work() to rtnl_trylock() and requeueing the work with a 1 jiffy delay if RTNL is contended. This change aims to prevent high CPU contention while waiting for RTNL lock. Linux kernel developers should verify patch application and monitor systems for potential memory leaks.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-74543 CVE Program record

    Publisher, destination, and source semantics verified

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

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

  • CVE-2026-74543 NVD vulnerability detail

    Publisher, destination, and source semantics verified

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

    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/080695e6f005e2396f1207fd69d24c442cb230c6

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

  • Source reference

    Unverified legacy reference

    URL: https://git.kernel.org/stable/c/52c753b46265243406690d980faa9514d3f53827

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

  • Source reference

    Unverified legacy reference

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

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

  • Source reference

    Unverified legacy reference

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

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

  • Source reference

    Unverified legacy reference

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

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

  • Source reference

    Unverified legacy reference

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

    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.