Quick answers
- Is CVE-2026-74705 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-74705 being exploited in the wild.
- How severe is CVE-2026-74705?
- Critical severity, with a CVSS score of 10, published 22 August 2026.
- Which products and versions are affected?
- Linux Kernel affected versions spanning from 2.6.11 through current mainline (6.x series); upstream fix commit d0f86fb36eb260abd10007b62c9dcc1028e03e61.
- Is there a fix for CVE-2026-74705?
- A patch was published on 2026-08-19: Fix committed to stable kernel trees Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-74705 attacked?
- It is attacked over the network, in an operating system.
- Am I affected by CVE-2026-74705?
- Check whether you run Linux Kernel at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the __skb_udp_tunnel_segment() function in net/ipv4/udp_offload.c. The function retrieves a UDP header pointer before ensuring the tunnel header is present in the socket buffer (skb) head. A subsequent pskb_may_pull() call may reallocate the skb->head, invalidating the saved UDP header pointer, leading to a use-after-free condition. The fix reorders the operations to obtain the UDP header pointer after the pull operation completes. This is a memory safety issue in kernel packet processing that is network-reachable with no authentication required.
Affected products
- Linux Linux kernel affected versions spanning from 2.6.11 through current mainline (6.x series); upstream fix commit d0f86fb36eb260abd10007b62c9dcc1028e03e61
Timeline
- 2026-08-22: disclosed: CVE-2026-74705 published
- 2026-08-19: patched: Fix committed to stable kernel trees