CVE-2022-36660: xhyve commit dfbe09b was discovered to contain a stack buffer overflow via the component pci_vtrnd_notify().

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2022-36660 is a critical-severity flaw (CVSS 9.8) affecting xhyve. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

xhyve commit dfbe09b was discovered to contain a stack buffer overflow via the component pci_vtrnd_notify().

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.0% (top 37%)
CISA exploited list	No
Weakness	CWE-787
Published	2022-09-07
Last modified	2026-06-17

Publisher (CNA): MITRE · Vendor: xhyve project

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2022-09-07 17:15 UTCPublished CVE record published
2026-06-17 04:53 UTCUpdated Record last modified

xhyve project xhyve DOWNGRADE

Affected: 2021-10-02

Fixed in: no fixed release known

Safe to downgrade to: a release before 2021-10-02

1. Check installed version

apt-cache policy xhyve || rpm -q xhyve || xhyve --version

2. No fixed release: DOWNGRADE to a release before 2021-10-02 (Debian / Ubuntu)

apt-cache madison xhyve sudo apt install xhyve=<VERSION_BEFORE_2021-10-02> sudo apt-mark hold xhyve

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list xhyve sudo dnf downgrade xhyve-<VERSION_BEFORE_2021-10-02> sudo dnf versionlock add xhyve

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-36660?

xhyve: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2022-36660 being exploited?

CVE-2022-36660 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-36660 affect?

CVE-2022-36660 affects xhyve. Severity is critical (CVSS 9.8). xhyve commit dfbe09b was discovered to contain a stack buffer overflow via the component pci_vtrnd_notify().

How urgent is CVE-2022-36660?

Priority 60/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

Related CVEs

CVE-2022-36661 MEDIUM 6.5 DOWNGRADE xhyve commit dfbe09b was discovered to contain a NULL pointer dereference via the component vi_pci_read()
CVE-2022-36659 MEDIUM 6.5 DOWNGRADE xhyve commit dfbe09b was discovered to contain a NULL pointer dereference via the component vi_pci_write()
CVE-2022-35867 MEDIUM 6.7 DOWNGRADE This vulnerability allows local attackers to escalate privileges on affected installations of xhyve

References

← Back to latest CVEs