Skip to main content

Over 150 LLM Providers · Over 5,300 Models The most extensible AI-powered pentesting platform. Open source. Star on GitHub

CVE-2026-72405

7.8 · HIGH
Published Aug 15, 2026 EPSS 0.13% (3th pctl)

Overview

CVE-2026-72405 is a high-severity vulnerability. It was published on August 15, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

Technical Description

In the Linux kernel, the following vulnerability has been resolved:

net: udp_tunnel: prevent double queueing in udp_tunnel_nic_device_sync

Yue Sun reported a use-after-free and debugobjects warning in

udp_tunnel_nic_device_sync_work() during concurrent device operations.

The workqueue core clears the internal pending bit before invoking the

worker. At that point, a concurrent thread can queue the work again.

When the already running worker eventually clears the work_pending flag

to 0, it mistakenly clears the flag for the newly queued instance.

udp_tunnel_nic_unregister() then observes work_pending as 0 and frees

the structure while the second work item is still active in the queue,

leading to UAF.

Fix this by returning early in udp_tunnel_nic_device_sync() if

work_pending is already set, preventing redundant work queueing.

Remediation

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

Frequently Asked Questions

What is CVE-2026-72405?

CVE-2026-72405 is a high-severity vulnerability. It was published on August 15, 2026 and has a CVSS 3.1 base score of 7.8 (HIGH).

How severe is CVE-2026-72405?

This vulnerability has a CVSS 3.1 base score of 7.8, rated HIGH. It requires local or adjacent network access to exploit. Some level of privileges is required for exploitation.

How do I fix or remediate CVE-2026-72405?

Check the references section for vendor advisories, patches, and mitigation guidance. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.

How can CyberStrike help with CVE-2026-72405?

CyberStrike's AI-powered security agents can automatically detect CVE-2026-72405 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.