FreeBSD issued security advisory FreeBSD-SA-26:11.amd64 for CVE-2026-6386, a kernel flaw in the amd64 routine pmap_pkru_update_range() that mishandles 1GB large page mappings. The bug affects all supported FreeBSD versions on amd64 and arises when largepage mappings created with shm_create_largepage(3) are not handled correctly, causing a page directory page entry to be misinterpreted as a pointer to another page table page.
FreeBSD warned that an unprivileged local user could exploit the issue to make the kernel treat userspace memory as a page table page and overwrite memory the application should not be able to access, creating a serious path to memory corruption and potential privilege impact. The project said no workaround is available and advised administrators to upgrade to corrected branches released after 2026-04-21 and reboot affected systems; fixes were published for stable/15, releng/15.0, stable/14, releng/14.4, releng/14.3, stable/13, and releng/13.5.

Mallory correlates global threat intelligence with your attack surface — know if you’re exposed before adversaries strike.
2 events from the most recent confirmed update back to the earliest known activity.
FreeBSD issued corrected stable and release branches dated after 2026-04-21 for stable/15, releng/15.0, stable/14, releng/14.4, releng/14.3, stable/13, and releng/13.5. The advisory said there is no workaround and recommended upgrading and rebooting affected systems.
FreeBSD published security advisory FreeBSD-SA-26:11.amd64 for CVE-2026-6386, describing an amd64 kernel bug in pmap_pkru_update_range() that mishandles 1GB large page mappings. The flaw affects all supported FreeBSD versions on amd64 and could allow an unprivileged user to make the kernel treat userspace memory as a page table page and overwrite otherwise inaccessible memory.
Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.
2 references tracked. Mallory keeps watching after this page renders.
Map indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.