Jail escape via cross-jail directory descriptor exchange
Published Mar 9, 2026 · Updated Mar 9, 2026
Jail escape in FreeBSD allows local users controlling two cooperating jails to gain full access to the host filesystem. A jailed process accepts a directory descriptor exchanged over a Unix domain socket from a sibling jail, and pathname lookup continues when it never encounters the recipient jail root. Exploitation requires two controlled jails sharing a nullfs mount where a Unix socket can be installed; escape permits reading and writing files outside the jail.
Summary
What happened
Jail escape in FreeBSD allows local users controlling two cooperating jails to gain full access to the host filesystem. A jailed process accepts a directory descriptor exchanged over a Unix domain socket from a sibling jail, and pathname lookup continues when it never encounters the recipient jail root. Exploitation requires two controlled jails sharing a nullfs mount where a Unix socket can be installed; escape permits reading and writing files outside the jail.
The record
- CVE
- CVE-2025-15576
- Published
- Mar 9, 2026
- Updated
- Mar 9, 2026
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-790, CWE-269, CWE-488, T1611
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 9, 2026CVE publishedPublication date reported by the CVE source.
- Mar 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=13.5-RELEASE <p10
- Affected versionversion=14.3-RELEASE <p9
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo