Panic or LPE via prison refcount underflow
Published Aug 19, 2026 · Updated Aug 20, 2026
Reference count underflow in FreeBSD before 15.0-RELEASE-p11 and 15.1-RELEASE-p1 allows local users to crash the host via failed jail descriptor lookups. In kern_jail_set() and kern_jail_get(), the JAIL_AT_DESC path drops the caller's current prison reference before jaildesc_find(); if lookup fails, the error path releases that same reference again, underflowing the prison refcount and leaving the prison structure eligible to be freed while still referenced. An unprivileged local user can reach the bug; on the jail host it generally causes an immediate panic, while a process already confined in a jail may be able to turn the stale prison reference into privilege escalation.
Summary
What happened
Reference count underflow in FreeBSD before 15.0-RELEASE-p11 and 15.1-RELEASE-p1 allows local users to crash the host via failed jail descriptor lookups. In kern_jail_set() and kern_jail_get(), the JAIL_AT_DESC path drops the caller's current prison reference before jaildesc_find(); if lookup fails, the error path releases that same reference again, underflowing the prison refcount and leaving the prison structure eligible to be freed while still referenced. An unprivileged local user can reach the bug; on the jail host it generally causes an immediate panic, while a process already confined in a jail may be able to turn the stale prison reference into privilege escalation.
The record
- CVE
- CVE-2026-49419
- Published
- Aug 19, 2026
- Updated
- Aug 20, 2026
- Vendor
- The FreeBSD Project
- Product
- FreeBSD
- Classifications
- CWE-911, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 19, 2026CVE publishedPublication date reported by the CVE source.
- Aug 20, 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=15.0-RELEASE <p11
- Affected versionversion=15.1-RELEASE <p1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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