Skip to main content
Mallory
HighVulnerability

CVE-2025-15576: FreeBSD jail/chroot escape via directory file descriptor exchange across sibling jails

Published Mar 9, 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.5High · v3.1
EPSS0.13%2nd percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2025-15576CWE-863

CVE-2025-15576 is a FreeBSD jail subsystem flaw that can allow a jailed process to escape filesystem confinement (chroot-style restrictions) when directory file descriptors are exchanged between two sibling jails. In the vulnerable design, the kernel’s pathname lookup enforces jail-root containment by checking at each step whether traversal would descend below the current process’ jail root; if the jail root is not encountered, lookup continues. In a configuration where two sibling jails (with non-ancestor jail roots) share a directory via a nullfs mount and can communicate over a Unix domain socket, cooperating processes can pass directory descriptors. A process can receive a directory file descriptor that is outside/below its own jail root, and subsequent name lookups starting from that descriptor can bypass the jail-root containment checks, resulting in full filesystem access and effectively breaking jail/chroot isolation.

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 results in a jail/chroot escape with full filesystem access from within the jail, enabling unauthorized read/write access to the host (or otherwise out-of-jail) filesystem. This can facilitate modification of critical system files, data theft, and follow-on actions that may lead to broader host compromise depending on other local conditions and privileges.

Mitigation

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

No workaround is available per the advisory. Reduce exploitability by avoiding configurations where sibling jails share a nullfs-mounted directory that permits creation/use of Unix domain sockets and file-descriptor passing between jails. Additionally, ensure unprivileged users on the jail host cannot pass directory descriptors to jailed processes (this remains an administrative responsibility even after patching).

Remediation

Patch, then assume compromise.

Apply FreeBSD’s corrected code (a stable or releng/release-security branch dated after the correction date). For RELEASE systems, use freebsd-update fetch and freebsd-update install, then reboot. For source-based systems, apply the vendor patches (jail-14.patch for FreeBSD 14.3; jail-13.patch for FreeBSD 13.5) from https://security.FreeBSD.org/patches/SA-26:04/, rebuild the kernel, and reboot.

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-2025-15576 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2025-15576 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2025-15576?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2025-15576.
Is there a patch for CVE-2025-15576?
Apply FreeBSD’s corrected code (a stable or releng/release-security branch dated after the correction date). For RELEASE systems, use freebsd-update fetch and freebsd-update install, then reboot.
What products are affected by CVE-2025-15576?
Freebsd.
How severe is CVE-2025-15576?
CVE-2025-15576 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.13% (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 activity5Community discussion across Reddit, Mastodon, and other social sources.