Description
During execve(2) of a SUID binary, the new virtual address space is installed before the process credentials are updated. During this window, a process running as the same user can access the target process's memory via procfs or linprocfs, because the kernel's debugging permission check still saw the original credentials.

An unprivileged local user can exploit this race to modify the address space of a SUID binary before its credentials are elevated, potentially gaining full control of the affected system.
Published: 2026-08-19
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A race condition in the execve(2) system call for SUID binaries allows a local user to observe and modify the target process's memory between the new address space installation and the credential elevation. By exploiting this window, the attacker can alter the binary's virtual address space and inject code, ultimately achieving full control of the affected system. This flaw corresponds to CWE‑367, the classic Time‑of‑Check to Time‑of‑Use race. The vulnerability grants local privilege escalation and potentially full root access.

Affected Systems

The issue affects FreeBSD systems that implement the execve(2) handler with the described race condition. No specific version range is listed in the advisory, so all releases that contain a vulnerable SUID binary should be considered. The advisory references FreeBSD‑SA‑26:39.execve, implying that the fix applies to the current FreeBSD code base.

Risk and Exploitability

The advisory does not provide a CVSS score; EPSS is unavailable and KEV is not listed, which does not preclude the possibility of exploitation. The flaw is exploitable only by a local user who runs processes with the same UID as a vulnerable SUID binary and has access to procfs or linprocfs. Because the race window exists right after the memory mapping step but before credential elevation, an attacker can gain root privileges without interacting with network services, making the attack local but highly potent. The worst‑case impact is complete system compromise.

Generated by OpenCVE AI on August 19, 2026 at 06:24 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Install the security update for FreeBSD that addresses the execve race condition (see advisory FreeBSD‑SA‑26:39.execve).
  • After patching, remove or restrict SUID binaries that are not essential to system operation.
  • Disable or restrict procfs debugging permissions for non‑privileged users to prevent unintended memory access.

Generated by OpenCVE AI on August 19, 2026 at 06:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Wed, 19 Aug 2026 12:00:00 +0000

Type Values Removed Values Added
First Time appeared Freebsd
Freebsd freebsd
Vendors & Products Freebsd
Freebsd freebsd

Wed, 19 Aug 2026 05:00:00 +0000

Type Values Removed Values Added
Description During execve(2) of a SUID binary, the new virtual address space is installed before the process credentials are updated. During this window, a process running as the same user can access the target process's memory via procfs or linprocfs, because the kernel's debugging permission check still saw the original credentials. An unprivileged local user can exploit this race to modify the address space of a SUID binary before its credentials are elevated, potentially gaining full control of the affected system.
Title Local privilege escalation via execve(2) TOCTOU race
Weaknesses CWE-367
References

cve-icon MITRE

Status: PUBLISHED

Assigner: freebsd

Published:

Updated: 2026-08-19T04:38:24.391Z

Reserved: 2026-05-29T20:24:28.615Z

Link: CVE-2026-49415

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-08-19T05:17:03.830

Modified: 2026-08-19T05:17:03.830

Link: CVE-2026-49415

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-19T11:45:04Z

Weaknesses
  • CWE-367

    Time-of-check Time-of-use (TOCTOU) Race Condition