CVE-2025-15547
Privilege Escalation via Nullfs Mount Escape in FreeBSD Jails
Publication date: 2026-03-09
Last updated on: 2026-03-17
Assigner: FreeBSD
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 13.5 |
| freebsd | freebsd | 14.3 |
| freebsd | freebsd | 14.3 |
| freebsd | freebsd | 14.3 |
| freebsd | freebsd | 14.3 |
| freebsd | freebsd | 14.3 |
| freebsd | freebsd | 14.3 |
| freebsd | freebsd | 14.3 |
| freebsd | freebsd | 14.3 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-269 | The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "CVE-2025-15547 is a security vulnerability in FreeBSD's jail subsystem, which provides OS-level virtualization by restricting processes within confined environments."}, {'type': 'paragraph', 'content': 'Normally, jailed processes cannot mount filesystems, including the nullfs(4) pseudo-filesystem that allows mounting a directory at another point in the filesystem.'}, {'type': 'paragraph', 'content': 'However, if the allow.mount.nullfs option is enabled inside a jail, a privileged user can mount nullfs filesystems.'}, {'type': 'paragraph', 'content': "Due to a limitation in the kernel's path lookup logic, a privileged user inside such a jail can exploit this to escape the jail's filesystem root (chroot), gaining access to the full filesystem of the host or parent jail."}] [1]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': "This vulnerability allows a privileged user inside a FreeBSD jail with allow.mount.nullfs enabled to escape the jail's confinement."}, {'type': 'paragraph', 'content': 'Such an escape breaks the isolation intended by the jail, potentially exposing the entire host or parent jail filesystem to the attacker.'}, {'type': 'paragraph', 'content': 'This can lead to unauthorized access to sensitive files and data outside the jail, compromising system security and integrity.'}] [1]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves privileged users inside FreeBSD jails being able to mount nullfs filesystems if the allow.mount.nullfs option is enabled. Detection involves checking if any jails have the allow.mount.nullfs option enabled.
You can inspect jail configurations to see if allow.mount.nullfs is enabled. For example, use commands to list jail parameters or check jail configuration files.
- Check jail parameters with: jail -v or jls -v to list running jails and their parameters.
- Examine jail configuration files (e.g., /etc/jail.conf) for the allow.mount.nullfs option.
- Within a jail, verify if nullfs mounts are possible by attempting to mount a nullfs filesystem (requires privileged access).
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation is to ensure that the allow.mount.nullfs option is not enabled in any jail configurations, preventing jailed processes from mounting nullfs filesystems.
Additionally, apply the official patches provided by FreeBSD to fix the kernel path lookup limitation that allows jail escapes.
- Upgrade to patched FreeBSD stable or release branches dated after June 30, 2025 (for stable/14 and stable/13) or January 26-27, 2026 (for releng/14.3 and releng/13.5).
- Use freebsd-update to apply updates on supported platforms.
- Alternatively, download, verify, and apply source patches followed by recompiling the kernel.
No other workaround exists besides disabling allow.mount.nullfs or applying the patches.