-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 ============================================================================= FreeBSD-SA-26:90.vm Security Advisory The FreeBSD Project Topic: Privilege escalation via prefaulting on largepage mappings Category: core Module: vm Announced: 2026-11-17 Credits: OpenAI Security Research Team Credits: Albert // Vexera AI Affects: All supported versions of FreeBSD. Corrected: 2026-11-17 17:06:14 UTC (stable/15, 15.2-STABLE) 2026-11-17 17:08:31 UTC (releng/15.1, 15.1-RELEASE-p7) 2026-11-17 17:03:01 UTC (stable/14, 14.5-STABLE) 2026-11-17 17:05:23 UTC (releng/14.5, 14.5-RELEASE-p4) 2026-11-17 17:04:25 UTC (releng/14.4, 14.4-RELEASE-p13) CVE Name: CVE-2026-127744 For general information regarding FreeBSD Security Advisories, including descriptions of the fields above, security branches, and the following sections, please visit . I. Background POSIX shared memory objects created with shm_create_largepage(3) are backed by physically contiguous large pages, and are mapped using large page table entries. A process may ask the kernel to populate the page table entries for a mapping in advance, for example using the MAP_PREFAULT_READ flag of mmap(2) or the MADV_WILLNEED advice of madvise(2). II. Problem Description The kernel's prefaulting code was not aware of large page mappings, and entered their constituent base pages into the page tables individually. As a result, a process could obtain a mapping of a page belonging to a large page object after the object had been freed. III. Impact An unprivileged local user can exploit this to access freed physical memory and escalate privileges. IV. Workaround No workaround is available. V. Solution Upgrade your vulnerable system to a supported FreeBSD stable or release / security branch (releng) dated after the correction date, and reboot the system. Perform one of the following: 1) To update your vulnerable system installed from base system packages: Systems running a 15.0-RELEASE or later version of FreeBSD on the amd64 or arm64 platforms, which were installed using base system packages, can be updated via the pkg(8) utility: # pkg upgrade -r FreeBSD-base # shutdown -r +10min "Rebooting for a security update" 2) To update your vulnerable system installed from binary distribution sets: Systems running a RELEASE version of FreeBSD on the amd64 or arm64 platforms which were not installed using base system packages can be updated via the freebsd-update(8) utility: # freebsd-update fetch # freebsd-update install # shutdown -r +10min "Rebooting for a security update" 3) To update your vulnerable system via a source code patch: The following patches have been verified to apply to the applicable FreeBSD release branches. a) Download the relevant patch from the location below, and verify the detached PGP signature using your PGP utility. [FreeBSD 15.1] # fetch https://security.FreeBSD.org/patches/SA-26:90/vm-15.patch # fetch https://security.FreeBSD.org/patches/SA-26:90/vm-15.patch.asc # gpg --verify vm-15.patch.asc [FreeBSD 14.5] # fetch https://security.FreeBSD.org/patches/SA-26:90/vm-14.5.patch # fetch https://security.FreeBSD.org/patches/SA-26:90/vm-14.5.patch.asc # gpg --verify vm-14.5.patch.asc [FreeBSD 14.4] # fetch https://security.FreeBSD.org/patches/SA-26:90/vm-14.4.patch # fetch https://security.FreeBSD.org/patches/SA-26:90/vm-14.4.patch.asc # gpg --verify vm-14.4.patch.asc b) Apply the patch. Execute the following commands as root: # cd /usr/src # patch -E -p0 < /path/to/patch c) Recompile your kernel as described in and reboot the system. VI. Correction details This issue is corrected as of the corresponding Git commit hash in the following stable and release branches: Branch/path Hash Revision - ------------------------------------------------------------------------- stable/15/ 025ff8ca639b stable/15-n286884 releng/15.1/ bd77900ddc7c releng/15.1-n283688 stable/14/ e35e3525efa0 stable/14-n275589 releng/14.5/ 9b01955b2c68 releng/14.5-n274924 releng/14.4/ 25d1c8f40d25 releng/14.4-n273825 - ------------------------------------------------------------------------- Run the following command to see which files were modified by a particular commit: # git show --stat Or visit the following URL, replacing NNNNNN with the hash: To determine the commit count in a working tree (for comparison against nNNNNNN in the table above), run: # git rev-list --count --first-parent HEAD VII. References The latest revision of this advisory is available at -----BEGIN PGP SIGNATURE----- iQJPBAEBCgA5FiEEthUnfoEIffdcgYM7bljekB8AGu8FAmr82lsbFIAAAAAABAAO bWFudTIsMi41KzEuMTIsMCwzAAoJEG5Y3pAfABrv60kP/RAVH4Wu5fx0PmL7g/9A cehkB169sIwyLGDzfZhnP9cyzHFs4oCj1dS+A0P6hUpAQAOk7BXuYTNnQbNF6OWH sN6VhowcaDJgviuGRhjgPy+TM8qlptIuUNQKbY2P3bX5xdGk5pOSazpf6eORZF5j CUQgl2okNGYYpE4KIijTlkjOtBEOtEA88PHH7nOni73T3Z/sdT6fvWary2G7G0bw SME88C56qLT3UnBFBZ13DDq4imlM/1XtYUX7P3urX8nVRq1spuTBSdA3GjHh38Kv ON3NujvZc4Rw5oOExyN/ZGq2H6oJEj68xdvhjHC9C4EPQ35ecpI7GYSf+V1ISPE4 wNtoDdo3RbQ9/vSgeC4oGUbcPM2N+rx/7aX3DNt61l8z3cw48TX1uWS3c4ULD94c 5UKI/3VmAe+XGMhNgwXF0VW6c8qJBZ7HTq5lA9sBo5oLahvWjXSGmu1zJXVDAecY ee02l+gqaL/BLypzm9WR4xgo20o3cYIXPC0GrkPNKF/I5/q9fX1Ou/b2FR1czMKp ymyfvoyLnGTlPTkAYFlH81pPm64fuxFgwXR6GUBLxUf5Tkj2Ii0M6MZ7Mw4+LNMo nuULYLdjmC6OBu94WHhIDdIUqO459L2zsiOhngJ1ssg/HUn+LMFuwgtkl32SBJn3 BfML+RMPeh488EVxNyIV56cq =Npdo -----END PGP SIGNATURE-----