LiveActive security incident?Get immediate response
CVE Record

CVE-2022-36661: xhyve commit dfbe09b was discovered to contain a NULL pointer dereference via the component vi_pci_read().

xhyve commit dfbe09b was discovered to contain a NULL pointer dereference via the component vi_pci_read(). This vulnerability allows attackers to cause a Denial of Service via unspecified vectors.

MediumCVSS 6.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-36661 is a denial-of-service issue in xhyve. A NULL pointer dereference in vi_pci_read() can crash affected software, disrupting availability. The public record does not identify precise affected versions or attack vectors beyond the referenced commit, so exposure depends on whether an organization runs that vulnerable xhyve code.

Executive priority

Treat this as a moderate availability risk, not a confirmed data breach risk. Prioritize it for teams using xhyve in business-critical virtualization or development workflows. If xhyve is not present, document non-exposure and monitor vendor records for clarification.

Technical view

The CVE describes a CWE-476 NULL pointer dereference in xhyve commit dfbe09b, specifically vi_pci_read(). CVSS 3.1 is 6.5 with availability impact high, low attack complexity, low privileges, and no user interaction. The public source bundle does not name patched versions, affected CPEs, or detailed trigger conditions.

Likely exposure

Exposure is likely limited to environments running xhyve or downstream builds containing commit dfbe09b. The CVE record lists affected vendor, product, versions, and CPEs as unavailable, so asset confirmation is required before prioritizing broadly.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation. The vulnerability is described as denial of service through unspecified vectors, so assume crash potential where vulnerable xhyve code is reachable by a low-privileged actor until vendor guidance clarifies scope.

Researcher notes

The evidence is sparse: one public disclosure reference, no affected CPEs, no named fixed version, and unspecified vectors. Research should focus on source-code lineage, downstream packaging, and operational reachability rather than assuming broad internet exposure or active exploitation.

Mitigation direction

  • Inventory xhyve deployments and downstream forks for commit dfbe09b or matching vi_pci_read() code.
  • Check xhyve maintainer or downstream vendor guidance for fixed builds before changing production systems.
  • Restrict access to systems and interfaces that can exercise xhyve runtime or management functionality.
  • Increase monitoring for xhyve crashes or availability failures in affected virtualization hosts.

Validation and detection

  • Confirm whether any production image, package, or source checkout includes xhyve commit dfbe09b.
  • Review crash logs for NULL pointer dereference indicators involving vi_pci_read().
  • Map users or services with low-privilege access to affected xhyve functionality.
  • Verify any upgraded or replaced build no longer contains the vulnerable code path.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-476: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-36661 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
6.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
6.5CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H2.83.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.5Medium
CVSS 3.1 vector shape for CVE-2022-36661Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-476 · source CWE mapping

NULL Pointer Dereference

NULL Pointer Dereference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.