Skip to content
Fencer Intel
high 7.8

CVE-2022-42332 json

x86 shadow plus log-dirty mode use-after-free In environments where host assisted address translation is necessary but Hardware Assisted Pa…

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

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

Summary

x86 shadow plus log-dirty mode use-after-free In environments where host assisted address translation is necessary but Hardware Assisted Paging (HAP) is unavailable, Xen will run guests in so called shadow mode. Shadow mode maintains a pool of memory used for both shadow page tables as well as auxiliary data structures. To migrate or snapshot guests, Xen additionally runs them in so called log-dirty mode. The data structures needed by the log-dirty tracking are part of aformentioned auxiliary data. In order to keep error handling efforts within reasonable bounds, for operations which may require memory allocations shadow mode logic ensures up front that enough memory is available for the worst case requirements. Unfortunately, while page table memory is properly accounted for on the code path requiring the potential establishing of new shadows, demands by the log-dirty infrastructure were not taken into consideration. As a result, just established shadow page tables could be freed again immediately, while other code is still accessing them on the assumption that they would remain allocated.

Patch / fix

  • xen Debian 14, Debian 13, Debian 12 4.17.0+74-g3eac216e6e-1

debian advisories DEBIAN-CVE-2022-42332

  • xen SLE Module for Server Applications 15 SP4, SLE Module for Basesystem 15 SP4, SLE Micro 5.4 +3 more 4.16.3_06-150400.4.25.1
  • xen SLES for SAP 15 SP2, SLES 15 SP2-LTSS, SLE High Performance Computing 15 SP2-LTSS +1 more 4.13.4_20-150200.3.71.1
  • xen SLES for SAP 12 SP4, SLES 12 SP4-LTSS, SLES 12 SP4-ESPOS +2 more 4.11.4_38-2.89.1
  • xen SLES for SAP 15 SP3, SLES 15 SP3-LTSS, SLE Real Time 15 SP3 +7 more 4.14.5_12-150300.3.48.1
  • xen SLES 12 SP2-BCL 4.7.6_32-43.104.1
  • xen SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 4.12.4_34-3.88.1
  • xen SLES for SAP 15 SP1, SLES 15 SP1-LTSS, SLE High Performance Computing 15 SP1-LTSS 4.12.4_34-150100.3.86.1

suse advisories SUSE-SU-2023:0848-2SUSE-SU-2023:0862-1SUSE-SU-2023:0859-1SUSE-SU-2023:0858-1SUSE-SU-2023:0848-1SUSE-SU-2023:0847-1

  • xen openSUSE Tumbleweed 4.17.0_06-1.1

opensuse advisories openSUSE-SU-2024:12833-1

  • xen Alpine 3.15 4.15.5-r0
  • xen Alpine 3.17, Alpine 3.16 4.16.4-r0
  • xen Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 4.17.0-r5

alpine advisories ALPINE-CVE-2022-42332

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-42332 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-42332 updated cvss 7.5

xen: Xen Security Advisory

  • 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

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

CVSS scores

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

Affected products

  • Xen xen

Classification

Weakness

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.