CVE-2025-15576
HIGHDescription
If two sibling jails are restricted to separate filesystem trees, which is to say that neither of the two jail root directories is an ancestor of the other, jailed processes may nonetheless be able to access a shared directory via a nullfs mount, if the administrator has configured one. In this case, cooperating processes in the two jails may establish a connection using a unix domain socket and exchange directory descriptors with each other. When performing a filesystem name lookup, at each step of the lookup, the kernel checks whether the lookup would descend below the jail root of the current process. If the jail root directory is not encountered, the lookup continues. In a configuration where processes in two different jails are able to exchange file descriptors using a unix domain socket, it is possible for a jailed process to receive a directory for a descriptor that is below that process' jail root. This enables full filesystem access for a jailed process, breaking the chroot. Note that the system administrator is still responsible for ensuring that an unprivileged user on the jail host is not able to pass directory descriptors to a jailed process, even in a patched kernel.
How to fix
No published remediation has been found for this vulnerability's affected products yet.
Mitigation guidance may be in the linked vendor advisories in the References section below.
TridentStack Control tracks known vulnerabilities across your Windows, macOS, and Linux fleet and shows the fix as soon as one is published. See how it works
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 2% of all known CVEs.
References
Related Vulnerabilities
Other CWE-269 (Improper Privilege Management) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2017-12635 | Critical | 9.8 | 100% | - | Fix |
| CVE-2022-24637 | Critical | 9.8 | 99% | - | Fix |
| CVE-2017-5689 | Critical | 9.8 | 92% | KEV | Fix |
| CVE-2020-3243 | Critical | 9.8 | 88% | - | - |
| CVE-2024-21888 | High | 8.8 | 87% | - | - |
| CVE-2022-0441 | Critical | 9.8 | 85% | - | Fix |
Common questions
How do I fix CVE-2025-15576?
No published fix for CVE-2025-15576 has been found yet. Check the linked vendor advisories for guidance as it becomes available.
Is CVE-2025-15576 being actively exploited?
Not that we know of. CVE-2025-15576 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.11% is the estimated probability that it will be exploited in the next 30 days. That is higher than 2% of all scored CVEs.
How severe is CVE-2025-15576?
CVE-2025-15576 has a CVSS v3 base score of 7.5, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
Embed a live status badge for CVE-2025-15576
Markdown
[](https://tridentstack.com/cve/CVE-2025-15576)HTML
<a href="https://tridentstack.com/cve/CVE-2025-15576"><img src="https://tridentstack.com/cve/badge/CVE-2025-15576.svg" alt="CVE-2025-15576"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-03-17.