CVE-2025-15576: FreeBSD jail/chroot escape via directory file descriptor exchange across sibling jails
- Vendor
- Freebsd
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.
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.
Exploits
No public exploits tracked yet. Mallory keeps watching.
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.
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.
Recent activity
10 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.