Description
The framebuffer device model's maximum resolution constants were duplicated between the framebuffer and RFB modules and had gotten out of sync. Additionally, writes to the framebuffer BAR could set arbitrary width and height values without validation, and the framebuffer BAR I/O and RFB rendering threads were not synchronized.

A malicious guest can crash the bhyve process or potentially execute arbitrary code in the host userspace context running the virtual machine, subject to bhyve's Capsicum sandbox.
Published: 2026-10-15
Score: 7 High
EPSS: < 1% Very Low
KEV: No
Impact: Potential host userspace arbitrary code execution
Action: Apply Patch
AI Analysis

Impact

The vulnerability arises from duplicated maximum resolution constants between the framebuffer and RFB modules, unchecked writes to the framebuffer BAR that can set arbitrary width and height values, and lack of synchronization between the framebuffer BAR I/O and RFB rendering threads. These issues allow a malicious guest to crash the bhyve hypervisor process or execute arbitrary code in the host user‑space context that runs the virtual machine, subject to the limits imposed by bhyve’s Capsicum sandbox.

Affected Systems

The affected product is the bhyve hypervisor on FreeBSD systems. No specific version range is provided; the advisory applies to any release of bhyve on FreeBSD that contains the unpatched framebuffer device model.

Risk and Exploitability

The CVSS score of 7 indicates high severity, while the EPSS score of less than 1 percent indicates a very low likelihood of exploitation at the time of analysis. The vulnerability is not listed in the CISA KEV catalog. It is likely that an attacker must run a malicious guest with sufficient capabilities to trigger the vulnerability, exploiting the lack of validation and synchronization within the bhyve device firmware.

Generated by OpenCVE AI on October 16, 2026 at 22:02 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Update FreeBSD to a release that includes the bhyve framebuffer device model patch.
  • If an update is not yet available, run bhyve under a tighter Capsicum sandbox to restrict guest privileges and limit potential damage.
  • If the framebuffer or RFB modules are not required, disable them in the bhyve configuration to remove the attack surface.

Generated by OpenCVE AI on October 16, 2026 at 22:02 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 22:15:00 +0000

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

Thu, 15 Oct 2026 14:30:00 +0000

Type Values Removed Values Added
Metrics cvssV3_1

{'score': 7, 'vector': 'CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Thu, 15 Oct 2026 13:30:00 +0000

Type Values Removed Values Added
Description The framebuffer device model's maximum resolution constants were duplicated between the framebuffer and RFB modules and had gotten out of sync. Additionally, writes to the framebuffer BAR could set arbitrary width and height values without validation, and the framebuffer BAR I/O and RFB rendering threads were not synchronized. A malicious guest can crash the bhyve process or potentially execute arbitrary code in the host userspace context running the virtual machine, subject to bhyve's Capsicum sandbox.
Title Multiple vulnerabilities in bhyve device models
Weaknesses CWE-362
References

cve-icon MITRE

Status: PUBLISHED

Assigner: freebsd

Published:

Updated: 2026-10-16T03:56:36.774Z

Reserved: 2026-09-28T13:33:02.324Z

Link: CVE-2026-101311

cve-icon Vulnrichment

Updated: 2026-10-15T13:39:00.567Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-10-15T08:16:36.423

Modified: 2026-10-16T04:18:11.237

Link: CVE-2026-101311

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T22:15:06Z

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')