Skip to main content
Mallory
HighVulnerability

CVE-2026-49428: Use-after-free in FreeBSD POSIX largepage shared memory handling

Published Aug 19, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS8.4High · v3.1
EPSS0.34%28th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-49428CWE-416

CVE-2026-49428 is a local kernel memory-safety vulnerability in FreeBSD's handling of POSIX largepage shared memory objects. Certain system calls, including open(2) when invoked with O_TRUNC and fspacectl(2), could incorrectly free memory associated with largepage objects even though those operations are not permitted for such objects. The implementation failed to verify that the target object type disallowed these operations, resulting in an invalid free and a subsequent use-after-free condition in kernel memory management. An unprivileged local user may trigger the flaw and gain access to freed kernel memory, creating a path to privilege escalation.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow an unprivileged local user to access freed kernel memory and leverage the resulting use-after-free condition for local privilege escalation, potentially obtaining elevated privileges up to root. The flaw affects kernel memory integrity and may also introduce broader system stability risk depending on exploitation behavior.

Mitigation

If you can’t patch tonight, do this now.

No workaround is available. Risk reduction is limited to restricting untrusted local access until patched systems can be deployed.

Remediation

Patch, then assume compromise.

Update FreeBSD to a fixed supported release or security patch level. Reported fixed versions include 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16. Where binary updates are used, apply the vendor-provided operating system updates and reboot. Where source-based maintenance is used, apply the corresponding vendor patch, rebuild the affected kernel components as required, and reboot the system.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
FreebsdFreebsdoperating_system
FAQ

Frequently asked questions

Is CVE-2026-49428 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2026-49428 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-49428?
As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-49428.
Is there a patch for CVE-2026-49428?
Update FreeBSD to a fixed supported release or security patch level. Reported fixed versions include 15.1-RELEASE-p1, 15.0-RELEASE-p11, 14.4-RELEASE-p7, and 14.3-RELEASE-p16.
What products are affected by CVE-2026-49428?
Freebsd.
How severe is CVE-2026-49428?
CVE-2026-49428 has a CVSS v3.1 score of 8.4 (High) and an EPSS score of 0.34% (28th percentile) as of Sep 25, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.