Microsoft · udp_tunnel: fix NULL deref caused by udp_sock_create6 when CONFIG_IPV6=n
Affects MicrosoftSource GCVE Database
Not known to be exploited.
Data as of 1 Nov 2026, 11:02 UTC
Rated Medium by Threat Radar's AI analysis · No CVSS score from NVD or the CNA
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Exploitation evidence
Disclosed: evidence found.
CVE published 25 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 24 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Security Response Center Microsoft | Affected
| Fixed in– |
Description
This vulnerability involves a NULL pointer dereference caused by the function udp_sock_create6 when the CONFIG_IPV6 configuration is disabled (CONFIG_IPV6=n). It affects Microsoft software version 2.0. The issue may lead to application crashes or denial of service conditions due to improper handling of UDP socket creation in IPv6-disabled environments.