Skip to main content
Mallory
MediumVulnerability

CVE-2026-6386: FreeBSD amd64 Memory Corruption in Protection-Key Large-Page Handling

Published Apr 22, 2026 · Updated 27 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS6.2Medium · v3.1
EPSS0.20%10th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Freebsd
IdentifiersCVE-2026-6386CWE-843

CVE-2026-6386 is a memory-corruption vulnerability in the FreeBSD amd64 kernel routine pmap_pkru_update_range(), which updates page table entries when applying memory protection keys to an address range. The routine fails to recognize 1 GB large-page mappings created through shm_create_largepage(3), instead treating the corresponding page directory entry as a pointer to another page table page. An unprivileged local user can consequently cause the kernel to interpret userspace memory as page table entries and overwrite memory that the application would otherwise be unable to access. All FreeBSD versions supported at the time of disclosure were affected on amd64.

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.

An unprivileged local user can violate memory-access protections by inducing kernel-mediated writes to memory outside the application's permitted access. This compromises memory integrity. Privilege escalation and arbitrary code execution are not established by the available information.

Mitigation

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

No workaround is available according to FreeBSD security advisory FreeBSD-SA-26:11.amd64. Install the corrected kernel and reboot.

Remediation

Patch, then assume compromise.

Upgrade to a corrected FreeBSD release: 15.0-RELEASE-p6, 14.4-RELEASE-p2, 14.3-RELEASE-p11, or 13.5-RELEASE-p12, or a later supported release containing the fix. Alternatively, update to a stable/15, stable/14, or stable/13 revision containing the April 21, 2026 corrections. Base-package installations can use 'pkg upgrade -r FreeBSD-base'; binary-distribution installations can use 'freebsd-update fetch' followed by 'freebsd-update install'. Source-based installations should apply the appropriate security patch and rebuild and install the corrected kernel. Reboot after updating.

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-6386 exploited in the wild?
As of Oct 23, 2026, Mallory has no reports of CVE-2026-6386 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-6386?
As of Oct 23, 2026, Mallory has found no public exploit for CVE-2026-6386.
Is there a patch for CVE-2026-6386?
Upgrade to a corrected FreeBSD release: 15.0-RELEASE-p6, 14.4-RELEASE-p2, 14.3-RELEASE-p11, or 13.5-RELEASE-p12, or a later supported release containing the fix. Alternatively, update to a stable/15, stable/14, or stable/13 revision containing the April 21, 2026 corrections.
What products are affected by CVE-2026-6386?
Freebsd.
How severe is CVE-2026-6386?
CVE-2026-6386 has a CVSS v3.1 score of 6.2 (Medium) and an EPSS score of 0.20% (10th percentile) as of Oct 23, 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 activity6Community discussion across Reddit, Mastodon, and other social sources.