LiveActive security incident?Get immediate response
CVE Record

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

xhyve commit dfbe09b was discovered to contain a NULL pointer dereference via the component vi_pci_write(). 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

This CVE describes a crash condition in xhyve, a virtualization component, caused by a NULL pointer dereference in vi_pci_write(). The stated impact is denial of service: an attacker could cause affected xhyve instances to stop working. The public record does not name affected versions, fixed versions, or confirmed exploitation.

Executive priority

Treat this as a moderate availability risk, not a confirmed breach indicator. Prioritize it where xhyve supports important services or where outages would affect customer operations. The main gap is uncertainty: public sources do not identify fixed versions, so teams need targeted inventory and vendor follow-up.

Technical view

CVE-2022-36659 is a CWE-476 NULL pointer dereference in xhyve commit dfbe09b, specifically in vi_pci_write(). The CVSS 3.1 score is 6.5 with availability impact only. The CVE describes unspecified denial-of-service vectors; it does not provide affected CPEs, product versions, a patch reference, or exploit details.

Likely exposure

Exposure is likely limited to environments running xhyve builds that include commit dfbe09b. The CVE data lists affected vendor, product, versions, and CPEs as unavailable, so asset teams must verify exposure by build provenance rather than automated CPE matching.

Exploitation context

No source in the bundle supports active exploitation. The CVE is not listed as KEV. The CVSS vector indicates network attack vector, low privileges, and no user interaction, but the public description only says unspecified vectors and does not explain a trigger path.

Researcher notes

The useful technical detail is narrow: vi_pci_write() in xhyve commit dfbe09b can dereference NULL, producing denial of service. The public bundle does not disclose a specific vector, proof of exploitation, affected release range, or patch commit. Validation should focus on commit-level exposure and crash telemetry.

Mitigation direction

  • Check upstream xhyve guidance for a fixed revision or advisory.
  • Avoid running builds known to include commit dfbe09b where possible.
  • Restrict access to systems or interfaces that can reach affected xhyve functionality.
  • Monitor vendor or project releases for remediation details.
  • Prioritize availability safeguards for workloads dependent on xhyve.

Validation and detection

  • Inventory systems using xhyve and record exact build commits.
  • Confirm whether deployed builds include commit dfbe09b.
  • Review dependency and image provenance where packaged versions hide commit details.
  • Check monitoring for unexplained xhyve crashes or availability interruptions.
  • Do not assume scanner coverage without matching CPE or version data.
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-36659 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-36659Attack 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.