Skip to main content
Mallory
HighVulnerability

CVE-2026-58094: FreeBSD POSIX Shared-Memory Large-Page Configuration TOCTOU Privilege Escalation

Published Aug 26, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS0.12%2nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-58094CWE-367 · Time-of-check Time-of-use (TOCTOU)…

CVE-2026-58094 is a time-of-check to time-of-use race condition in FreeBSD POSIX shared-memory large-page configuration. The FIOSSHMLPGCNF ioctl(2), which is intended to configure a large-page shared-memory object's page size before memory allocation, checked whether a page size had already been configured without holding the object's rangelock. Concurrent callers could both observe the object as unconfigured and apply conflicting page-size settings, corrupting the object's configuration state. The condition can be exploited by a local unprivileged user for privilege escalation.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local unprivileged attacker to escalate privileges. The vulnerability is rated CVSS v3.0 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), indicating potential high impact to confidentiality, integrity, and availability within the affected security authority.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available. Restrict local access to affected systems and limit access by untrusted users until the security update can be applied.

Remediation

Patch, then assume compromise.

Install the applicable FreeBSD security updates and reboot. Fixed releases are FreeBSD 15.1-RELEASE-p3, 15.0-RELEASE-p13, and 14.4-RELEASE-p9. Systems should otherwise upgrade to a supported stable or release/security branch incorporating the correction; base-package installations can update through the FreeBSD base-package mechanism, and applicable binary-set installations can use FreeBSD's update utility.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-58094 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-58094 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-58094?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-58094.
Is there a patch for CVE-2026-58094?
Install the applicable FreeBSD security updates and reboot. Fixed releases are FreeBSD 15.1-RELEASE-p3, 15.0-RELEASE-p13, and 14.4-RELEASE-p9.
What products are affected by CVE-2026-58094?
Freebsd.
How severe is CVE-2026-58094?
CVE-2026-58094 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 0.12% (2nd percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.