Loading vulnerability…
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.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
High-severity time-of-check to time-of-use race condition in FreeBSD POSIX shared memory that enables local privilege escalation.
A high-severity local privilege-escalation TOCTOU race in FreeBSD's POSIX shared-memory large-page configuration via the FIOSSHMLPGCNF ioctl(2). Concurrent callers can configure conflicting page sizes because the configuration check lacks the required rangelock.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.