# CVE-2026-15449: TOCTOU double copyin in illumos dld ioctl handling causes kernel heap corruption

> A race condition in illumos kernel ioctl handling allows local attackers to corrupt kernel memory, causing system panics or potential code execution.

- **Severity:** Medium 5.8 (`CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-5jqp-7hrf-w792

## What is CVE-2026-15449?

CVE-2026-15449 is a medium-severity vulnerability in OmniOS, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition), CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2026-15449?


## How do I fix CVE-2026-15449?

No fix has been published for CVE-2026-15449 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-15449 being exploited?

There is no known exploitation of CVE-2026-15449 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-15449 and fix it if it is affected.

What it is: CVE-2026-15449 is a medium-severity vulnerability in OmniOS, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-15449 in the wild and no public exploit code.

Affected product: OmniOS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-15449/ (Markdown: https://insights.sbomify.com/CVE-2026-15449/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-15449
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-15449
- OSV: https://osv.dev/vulnerability/CVE-2026-15449

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-15449/
Summaries are generated and may contain mistakes; the official description above is the record.