Skip to content
Fencer Intel
high 7.5

CVE-2022-42330 json

Guests can cause Xenstore crash via soft reset When a guest issues a "Soft Reset" (e.g.

published 3y ago modified 4mo ago also EUVD-2022-45405

cvss
7.5
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.4%
EPSS 1.4% chance of exploitation in 30 days, percentile 72%
public exploits
0
none known

Summary

Guests can cause Xenstore crash via soft reset When a guest issues a "Soft Reset" (e.g. for performing a kexec) the libxl based Xen toolstack will normally perform a XS_RELEASE Xenstore operation. Due to a bug in xenstored this can result in a crash of xenstored. Any other use of XS_RELEASE will have the same impact.

Patch / fix

  • xen Debian 14, Debian 13, Debian 12 4.17.0+24-g2f8851c37f-2

debian advisories DEBIAN-CVE-2022-42330

  • xen openSUSE Tumbleweed 4.17.0_04-1.1

opensuse advisories openSUSE-SU-2024:12644-1

  • xen Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 4.17.0-r2

alpine advisories ALPINE-CVE-2022-42330

Alpine secdb © Alpine Linux, from https://secdb.alpinelinux.org via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

Is CVE-2022-42330 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2022-42330 updated cvss 5.6

xen: guests can cause Xenstore crash via soft reset

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Affected products

  • Xen xen

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.