PatchSiren cyber security CVE debrief
CVE-2026-49427 FreeBSD CVE debrief
An unprivileged local user can exploit CVE-2026-49427 to access freed kernel memory, potentially escalating privileges. This issue affects multiple FreeBSD versions, including 14.3, 14.4, 15.0, and 15.1. The vulnerability stems from the improper handling of largepage shared memory objects when transmitted with the SF_NOCACHE flag. System administrators and security teams should assess exposure and prioritize patching for affected FreeBSD versions. The vulnerability can be exploited by unprivileged local users, potentially leading to privilege escalation.
- Vendor
- FreeBSD
- Product
- Unknown
- CVSS
- HIGH 8.8
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-19
- Original CVE updated
- 2026-09-01
- Advisory published
- 2026-08-19
- Advisory updated
- 2026-09-01
Who should care
System administrators and security teams responsible for FreeBSD systems should assess exposure and prioritize patching. This vulnerability can be exploited by unprivileged local users, potentially leading to privilege escalation.
Why it matters
CVE-2026-49427 allows unprivileged local users to access freed kernel memory, potentially escalating privileges. System administrators and security teams should assess exposure and prioritize patching for affected FreeBSD versions.
- Unprivileged local users can access freed kernel memory
- Potential privilege escalation
- Requires verification of affected versions and exposure
- Patching priority for FreeBSD systems
Technical summary
The vulnerability is caused by the improper handling of largepage shared memory objects when transmitted with the SF_NOCACHE flag. This can lead to an unprivileged local user accessing freed kernel memory, potentially escalating privileges. The vulnerability affects multiple FreeBSD versions, including 14.3, 14.4, 15.0, and 15.1. System administrators and security teams should assess exposure and prioritize patching for affected FreeBSD versions. The vulnerability can be exploited by unprivileged local users, potentially leading to privilege escalation.
Defensive priority
High
Recommended defensive actions
- Review and apply patches from the vendor
- Inventory systems for affected FreeBSD versions
- Monitor for potential exploitation attempts
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
Evidence notes
The CVE record and NVD vulnerability detail provide information on the vulnerability, its impact, and affected versions. A vendor advisory from [email protected] is also available. The vulnerability has been publicly disclosed and affects multiple FreeBSD versions. There is no evidence of public exploitation, but defenders should verify affected scope and exposure.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-49427 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-49427
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-49427 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-49427
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://security.freebsd.org/advisories/FreeBSD-SA-26:44.posixshm.asc
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.