# CVE-2026-58094: TOCTOU race in POSIX shared memory large page configuration

> A race condition in FreeBSD's POSIX shared memory configuration allows local attackers to escalate privileges by exploiting a TOCTOU flaw.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 26 Aug 2026
- **Updated:** 27 Aug 2026

## What is CVE-2026-58094?

CVE-2026-58094 is a high-severity vulnerability in Freebsd Freebsd, published on 26 Aug 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The FIOSSHMLPGCNF ioctl(2) operation configures the page size for a largepage shared memory object.  This is intended to be used immediately after creating the object, before any memory is allocated for the object.  The handler checked whether a page size had already been configured without holding the rangelock.  Two concurrent callers could both observe an unconfigured object and set conflicting page sizes, leaving the object in an inconsistent state.

An unprivileged local user can exploit this race to escalate privileges.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 1 product.


Products: Freebsd Freebsd.

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

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

## Is CVE-2026-58094 being exploited?

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

## Other vulnerabilities in Freebsd Freebsd

- [CVE-2018-17160](https://insights.sbomify.com/CVE-2018-17160/): Memory corruption in FreeBSD (critical 10.0)
- [CVE-2014-3954](https://insights.sbomify.com/CVE-2014-3954/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-4304](https://insights.sbomify.com/CVE-2006-4304/): Memory corruption in n/a (critical 10.0)
- [CVE-2006-0226](https://insights.sbomify.com/CVE-2006-0226/): Integer overflow in n/a (critical 10.0)
- [CVE-2004-0002](https://insights.sbomify.com/CVE-2004-0002/): Denial of service in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-58094 is a high-severity vulnerability in Freebsd Freebsd, published on 26 Aug 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-58094 in the wild and no public exploit code.

Affected product: Freebsd Freebsd. 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-58094/ (Markdown: https://insights.sbomify.com/CVE-2026-58094/index.md)
```

## Sources

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

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