cve.bz

CVE-2026-104113 omnios omnios: Double Free

5.4 mediumEPSS 0.1%Fix available

Medium (5.4) in omnios omnios. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
A double free in the IP management daemon (ipmgmtd) of OmniOS and SmartOS allows a local user to crash the daemon. When authorizing a door request that modifies interface configuration, ipmgmt_handler() in usr/src/cmd/cmd-inet/lib/ipmgmtd/ipmgmt_door.c frees the caller's credential with ucred_free() immediately after reading the user ID, and frees it a second time on the error path if the authorization check fails. An unprivileged local user who does not hold the solaris.network.interface.config authorization can send such a request, for example IPMGMT_CMD_RESETIF, to the ipmgmtd door, causing ipmgmtd to abort; repeated requests place the svc:/network/ip-interface-management service into maintenance, preventing IP interface configuration. The early free was introduced in 2014 to support lx-branded zones (OmniOS commit 4c170900) and is not present in upstream illumos-gate. It affects OmniOS r151020 and later, and SmartOS, prior to the fix.

Severity

CVSS 4.0

5.4 medium
CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:P
EPSS
0.1% (unchanged from 0.1% a week ago; 0.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 2nd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-415 Double Free
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • OmniOS OmniOS: fixed in r151058w
  • OmniOS OmniOS: fixed in r151056aw
  • OmniOS OmniOS: fixed in r151054bw

Ask an AI about this CVE

Show the promptExplain CVE-2026-104113 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-104113?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-104113?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-104113 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
OmniOSfrom r151020 before r151054
OmniOSfrom r151058 before r151058w
OmniOSfrom r151056 before r151056aw
OmniOSfrom r151054 before r151054bw

Fixed in

ProductFixed in
OmniOSr151058w
OmniOSr151056aw
OmniOSr151054bw

References

Check your stackJSON