CVE-2026-15449

TOCTOU double copyin in illumos dld ioctl handling causes kernel heap corruption

MEDIUM
5.8
CVSS Score
Published: July 16, 2026 at 07:27 PM UTC
Updated: July 17, 2026 at 07:55 PM UTC
3 products affected across 3 vendorsIllumos GateOmniOSSmartOS

Using illumos-gate by illumos?

Get instant alerts when new vulnerabilities affect illumos-gate - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.8
Exploit prediction
EPSS 0.1%
SSVC
No known exploit

Description

A time-of-check to time-of-use (TOCTOU) flaw in the illumos data-link pseudo-driver (dld) affects handling of the DLDIOC_GETMACPROP and DLDIOC_SETMACPROP ioctls on /dev/dld. drv_ioc_prop_common() in usr/src/uts/common/io/dld/dld_drv.c copies the dld_ioc_macprop_t ioctl header in once to read its pr_valsize field, sizes and allocates a kernel heap buffer from that value, and then copies the full request in a second time from the same unprivileged user address. A concurrent thread can enlarge pr_valsize between the two copyins, so the second copyin and the subsequent property handling write beyond the end of the undersized allocation and corrupt the kernel heap. An unprivileged local user, including one confined to a non-global zone that owns a datalink, can trigger this to panic the system. The resulting kernel heap corruption may be usable for further compromise.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

eae72b5b807baa9116e64502cbb278edf15f3146 ≤ v < 6959feb5b430411a4809b06c53dcdb42fb525eaceae72b5b807baa9116e64502cbb278edf15f3146
Vendor states this is fixed in 6959feb5b430411a4809b06c53dcdb42fb525eac (fixed)
any ≤ v < r151054r151054 ≤ v < r151054bjr151056 ≤ v < r151056ajr151058 ≤ v < r151058janyr151054r151056r151058
Affected range stops below r151054, so it looks safe — our inference, not a vendor statement
Affected range stops below r151054bj, so it looks safe — our inference, not a vendor statement
Affected range stops below r151056aj, so it looks safe — our inference, not a vendor statement
Affected range stops below r151058j, so it looks safe — our inference, not a vendor statement
any ≤ v < 202060709any
Affected range stops below 202060709, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

5.8MEDIUMillumos
Vector?

Quick Info

StatusDEFERRED
CWE
CWE-367CWE-122

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card