dbcve.org
FedoraOperating system · Fedoraproject

CVE-2022-23034

MEDIUM · 5.5 CVSS v3.1 Published 2022-01-25
Fix available
A fix is available. Upgrade to 4.13.0 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click Patch available

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 · unedited
A PV guest could DoS Xen while unmapping a grant To address XSA-380, reference counting was introduced for grant mappings for the case where a PV guest would have the IOMMU enabled. PV guests can request two forms of mappings. When both are in use for any individual mapping, unmapping of such a mapping can be requested in two steps. The reference count for such a mapping would then mistakenly be decremented twice. Underflow of the counters gets detected, resulting in the triggering of a hypervisor bug check.

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

A detailed technical summary for this CVE is being prepared.

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
FedoraOperating system
Affected:= 34
Debian LinuxOperating system
Affected:= 9.0= 11.0
XenOperating system
Affected:>= 3.2.0, < 4.13.0

CVSS 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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

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

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.

dbcve · scoped
Upgrade available Upgrade to 4.13.0 or later
Fixed in 4.13.0
Vendor patch xenbits.xenproject.org →
Recommended fix High confidence

Xen 4.13.0 or later; Fedora upgrade to 35+; Debian upgrade to 12 or apply vendor security patches

  1. 1. Identify the Xen hypervisor version currently running using 'xl info' or 'xm info' commands
  2. 2. For Xen: Upgrade to Xen 4.13.0 or later which contains the fix for XSA-394
  3. 3. For Fedora 34: Note that Fedora 34 reached end of life in 2022; migrate to a supported Fedora version (Fedora 35 or later) which includes patched Xen packages
  4. 4. For Debian 9.0 (Stretch) and 11.0 (Bullseye): Check Debian security advisories for XSA-394 patches; if unavailable, upgrade to Debian 12 or apply virtual machine isolation as a mitigation
  5. 5. After upgrading Xen, verify the version with 'xl info | grep xen_version'
  6. 6. Ensure PV guests with IOMMU enabled are tested after the upgrade to confirm grant unmapping functions correctly
Caveat Xen 4.13.0 may introduce compatibility changes with older PV guest kernels; test guest compatibility before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-23034 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-23034 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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