FreeBSDOperating system
CVE-2020-7467
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn FreeBSD 12.2-STABLE before r365767, 11.4-STABLE before r365769, 12.1-RELEASE before p10, 11.4-RELEASE before p4 and 11.3-RELEASE before p14 a number of AMD virtualization instructions operate on host physical addresses, are not subject to nested page table translation, and guest use of these instructions was not trapped.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceIn FreeBSD's bhyve hypervisor, certain AMD SVM virtualization instructions operate on host physical addresses without nested page table translation, and guest use of these instructions was not properly trapped. This allows a malicious guest VM to potentially access host physical memory directly, enabling VM escape attacks.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
FreeBSDOperating system
= 11.3= 11.4= 12.1= 12.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Physical
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify FreeBSD versionRun 'uname -r' or check /etc/os-release to get the installed FreeBSD version numberAffected if The version is 11.3, 11.4, 12.1, or 12.2 without the respective patches applied (p14 for 11.3, p4 for 11.4, p10 for 12.1, or r365767 for 12.2-STABLE)
-
Verify bhyve hypervisor is installedRun 'which bhyve' or check if the bhyve kernel module is loaded via 'kldstat | grep bhyve'Affected if bhyve is installed and the FreeBSD version falls within the vulnerable version range
-
Confirm AMD SVM virtualization is in useCheck if AMD-V (SVM) is enabled in the system BIOS/UEFI, or verify VM configuration files contain 'amd' or 'svm' processor settings for the guest VMsAffected if AMD SVM virtualization is enabled and the host FreeBSD version is in the affected list
-
Check for running guest VMsUse 'bhyvectl --list' or check for active bhyve processes via 'ps aux | grep bhyve'Affected if Any guest VMs are running on a vulnerable FreeBSD host with AMD SVM enabled
The system is affected if it runs a vulnerable FreeBSD version (11.3, 11.4, 12.1, or 12.2) with bhyve and AMD SVM virtualization enabled, allowing untrusted guest VMs to potentially escape and access host physical memory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate affected FreeBSD systems to patched versions: 12.2-STABLE after r365767, 11.4-STABLE after r365769, 12.1-RELEASE p10 or later, 11.4-RELEASE p4 or later, or 11.3-RELEASE p14 or later.
Fix this in FreeBSD
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-7467 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-7467 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data