Skip to main content

FreeBSD CVE-2026-58084

| EUVDEUVD-2026-62338 MEDIUM
Use of Uninitialized Resource (CWE-908)
2026-08-19 freebsd GHSA-p4v3-cw55-5mrc
5.5
CVSS 3.1 · Vendor: freebsd
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged local shell account
  2. Delivery
    Create POSIX timer with CLOCK_TAI via timer_create(2)
  3. Exploit
    Call timer_settime(2) to trigger missing error-check code path
  4. Execution
    Kernel copies uninitialized stack buffer to caller's userspace buffer
  5. Persist
    Extract kernel memory contents from returned itimerspec
  6. Impact
    Use leaked pointers for KASLR bypass or credential harvesting

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Variable initialization
Exploitation Conditions

Exploitation requires a valid low-privileged local user account on a FreeBSD 15.0-RELEASE (prior to p12) or 15.1-RELEASE (prior to p2) system where no UTC-TAI offset has been configured in the running kernel - this is the specific triggering condition identified in the description, as it causes realtimer_gettime() to return an error rather than populate the buffer. The attacker must be permitted to call timer_create(2) with CLOCK_TAI and timer_settime(2), which are available to unprivileged users by default on standard FreeBSD configurations. CVSS PR:L confirms authenticated low-privilege access is required; PR:N (unauthenticated) exploitation is not possible. Key limiting factors: requires local shell access (network-remote exploitation is ruled out by AV:L), affects only FreeBSD 15.x series (not earlier branches per available data), and the TAI offset absence is a common but not universal system state.

Impact

The NVD-assigned CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, score 5.5) is internally consistent with the described exploitation path: a low-privileged local account is sufficient, no user interaction is required, and only confidentiality is impacted. The EPSS score of 0.18% (8th percentile) indicates low near-term exploitation probability by automated threat actors, which aligns with the local-access requirement limiting the pool of viable attackers. No CISA KEV listing exists and no public PoC has been referenced in available intelligence sources, both signals that exploitation remains opportunistic rather than widespread. The real-world risk is bounded by the requirement for an interactive shell account - remote unauthenticated exploitation is not possible. That said, kernel stack leaks carry secondary risk: leaked data can contain KASLR slide values, pointer residuals, or cryptographic material that facilitate privilege escalation chains. The narrow affected version scope (FreeBSD 15.x only) and the triggering precondition (absence of TAI offset configuration) further constrain the realistic exposure population. Organizations running FreeBSD 15.x in multi-tenant or shared-hosting environments should treat this as moderate-priority patching.

Exploit ScenarioDerived

A low-privileged user with an interactive shell on an unpatched FreeBSD 15.x system writes a minimal C program that calls timer_create(CLOCK_TAI, ...) followed by timer_settime(2) with a target itimerspec. On a system without a configured TAI offset, the kernel silently fails to populate the old-timer buffer and copies raw stack contents back to the caller's struct itimerspec. The attacker reads the returned bytes, which may contain residual kernel pointer values, enabling KASLR bypass for a subsequent privilege escalation attempt. No public PoC has been identified at time of analysis.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 26, 2026

Kernel stack memory disclosure in FreeBSD 15.x exposes uninitialized data to unprivileged local users through a missing error-return check in the POSIX timer subsystem. When a CLOCK_TAI timer is created on a system lacking a configured UTC-TAI offset, the kernel function realtimer_gettime() fails silently, and the resulting uninitialized stack buffer is copied verbatim to userspace via timer_settime(2). Affected releases are FreeBSD 15.0-RELEASE prior to p12 and 15.1-RELEASE prior to p2; no public exploit or CISA KEV listing has been identified at time of analysis.

RemediationAI

The primary fix is upgrading to FreeBSD 15.1-RELEASE-p2 or FreeBSD 15.0-RELEASE-p12 as specified in FreeBSD Security Advisory SA-26:51 at https://security.freebsd.org/advisories/FreeBSD-SA-26:51.ktimer.asc. Apply patches using the standard freebsd-update(8) mechanism or rebuild the kernel from patched source. Where immediate patching is not feasible, restricting local shell access to the system reduces the attack surface, since exploitation requires a low-privileged account. Additionally, deploying system-call filtering policies (e.g., Capsicum capability mode or custom pledge-style restrictions) to prevent unprivileged processes from calling timer_create(2) with CLOCK_TAI would block the specific exploitation path, but may break applications legitimately using TAI-based timers. Patch application requires a kernel rebuild or reboot, which constitutes the primary operational trade-off.

Affected VersionsENISA

FreeBSD 15.1-RELEASE <p2
FreeBSD 15.0-RELEASE <p12

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is classified as CWE-908 (Use of Uninitialized Resource), rooted in the FreeBSD kernel's POSIX interval timer implementation. The syscall timer_settime(2) internally calls realtimer_gettime() to snapshot the previous timer value before updating it. When the timer's clock source is CLOCK_TAI - International Atomic Time, which requires a UTC-TAI leap-second offset to be present on the running kernel - realtimer_gettime() returns an error if that offset has not been configured. The code path did not check this return value, so the on-stack output buffer, never written by the failed function, was passed directly to copyout() and transferred to the calling userspace process. The affected CPE is cpe:2.3:a:freebsd:freebsd:*:*:*:*:*:*:*:* covering FreeBSD 15.x base system versions per EUVD-2026-62338 and FreeBSD Security Advisory SA-26:51.

Know when Freebsd gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (freebsd) PRIMARY 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 5.5 MEDIUM

Local access and a low-privileged account are required; only kernel stack data is disclosed with no integrity or availability impact.

3.1 AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (freebsd).

CVSS VectorVendor: freebsd

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Lifecycle Timeline

2
CVSS changed
Aug 26, 2026 - 20:23 NVD
5.5 (MEDIUM)
CVE Published
Aug 19, 2026 - 07:31 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

To retrieve the previous timer value, the kernel calls realtimer_gettime(), which obtains the current time for the timer's clock. For a timer using CLOCK_TAI this can fail when no TAI offset has been configured, but the error return was not checked, so the uninitialized output buffer was copied to userspace.

An unprivileged local user can obtain uninitialized kernel stack memory by creating a POSIX timer with CLOCK_TAI and calling timer_settime(2), potentially disclosing sensitive kernel data.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
Low
FreeBSD used in niche server and embedded deployments
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Defer
Exploitation· derived
None
System Exposure· derived
Small
Automatable· derived
No
Human Impact· derived
Medium

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2012-0217 HIGH POC
7.2 Jun 12

The x86-64 kernel system-call functionality in Xen 4.1.2 and earlier, as used in Citrix XenServer 6.0.2 and earlier and

CVE-2025-14558 HIGH POC
7.2 Mar 09

The rtsol(8) and rtsold(8) programs do not validate the domain search list options provided in router advertisement mess

CVE-2020-1967 HIGH POC
7.5 Apr 21

Server or client applications that call the SSL_check_chain() function during or after a TLS 1.3 handshake may crash due

CVE-2013-4854 HIGH POC
7.8 Jul 29

The RFC 5011 implementation in rdata.c in ISC BIND 9.7.x and 9.8.x before 9.8.5-P2, 9.8.6b1, 9.9.x before 9.9.3-P2, and

CVE-2024-6387 HIGH POC
8.1 Jul 01

Remote code execution in OpenSSH's sshd server (regression of CVE-2006-5051) allows unauthenticated remote attackers to

CVE-2019-6111 MEDIUM POC
5.9 Jan 31

An issue was discovered in OpenSSH 7.9. Rated medium severity (CVSS 5.9), this vulnerability is remotely exploitable, no

CVE-2023-48795 MEDIUM POC
5.9 Dec 18

The SSH transport protocol with certain OpenSSH extensions, found in OpenSSH before 9.6 and other products, allows remot

CVE-2013-2171 MEDIUM POC
6.9 Jul 02

The vm_map_lookup function in sys/vm/vm_map.c in the mmap implementation in the kernel in FreeBSD 9.0 through 9.1-RELEAS

CVE-2021-3449 MEDIUM
5.9 Mar 25

An OpenSSL TLS server may crash if sent a maliciously crafted renegotiation ClientHello message from a client. Rated med

CVE-2016-5766 HIGH POC
8.8 Aug 07

Integer overflow in the _gd2GetHeader function in gd_gd2.c in the GD Graphics Library (aka libgd) before 2.2.3, as used

CVE-2016-1879 HIGH POC
7.5 Jan 29

The Stream Control Transmission Protocol (SCTP) module in FreeBSD 9.3 before p33, 10.1 before p26, and 10.2 before p9, w

CVE-2020-7457 HIGH POC
8.1 Jul 09

In FreeBSD 12.1-STABLE before r359565, 12.1-RELEASE before p7, 11.4-STABLE before r362975, 11.4-RELEASE before p1, and 1

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy