CVE-2022-33746 json
P2M pool freeing may take excessively long The P2M pool backing second level address translation for guests may be of significant size.
published 4y ago modified 4mo ago also EUVD-2022-36785
- cvss
- 6.5
- 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 22%
- public exploits
- 0
- none known
Summary
P2M pool freeing may take excessively long The P2M pool backing second level address translation for guests may be of significant size. Therefore its freeing may take more time than is reasonable without intermediate preemption checks. Such checking for the need to preempt was so far missing.
Patch / fix
- xen Debian 14, Debian 13, Debian 12 4.16.2+90-g0d39a6d1ae-1
debian advisories DEBIAN-CVE-2022-33746
- xen SLES for SAP 12 SP4, SLES 12 SP4-LTSS, OpenStack Cloud Crowbar 9 +1 more 4.11.4_34-2.83.1
- xen SLES 12 SP2-BCL 4.7.6_28-43.98.1
- xen SLE Module for Server Applications 15 SP4, SLE Module for Basesystem 15 SP4, SLE Micro 5.3 +1 more 4.16.2_08-150400.4.16.1
- xen SLES for SAP 15 SP2, SLES 15 SP2-LTSS, SLES 15 SP2-BCL +6 more 4.13.4_16-150200.3.65.1
- xen SLE Module for Server Applications 15 SP3, SLE Module for Basesystem 15 SP3, SLE Micro 5.2 +3 more 4.14.5_08-150300.3.40.1
- xen SLES for SAP 15 SP1, SLES 15 SP1-LTSS, SLES 15 SP1-BCL +3 more 4.12.4_30-150100.3.80.1
- xen SLES for SAP 15, SLE High Performance Computing 15-LTSS, SLE High Performance Computing 15-ESPOS 4.10.4_40-150000.3.84.1
- xen SLES for SAP 12 SP5, SLES 12 SP5, SLE Software Development Kit 12 SP5 4.12.4_28-3.77.1
suse advisories SUSE-SU-2022:4241-1SUSE-SU-2022:4051-1SUSE-SU-2022:4007-1SUSE-SU-2022:3971-1SUSE-SU-2022:3947-1SUSE-SU-2022:3928-1
- xen openSUSE Tumbleweed 4.17.0_02-1.1
opensuse advisories openSUSE-SU-2024:12561-1
- xen Alpine 3.15, Alpine 3.14 4.15.4-r0
- xen Alpine 3.17, Alpine 3.16 4.16.3-r0
- xen Alpine 3.24, Alpine 3.23, Alpine 3.22 +4 more 4.17.0-r0
alpine advisories ALPINE-CVE-2022-33746
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-33746 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 FencerVendor 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-33746 updated cvss 6.5
xen: P2M pool freeing may take excessively long
-
Red Hat All currently supported Red Hat productsnot 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
0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H |
Affected products
- Xen xen
Classification
- Weakness
-
- CWE-404 Improper Resource Shutdown or Release
References
-
xenbits.xenproject.org
/xsa/advisory-410.txt
mitigation, patch, vendor-advisory
-
xenbits.xen.org
/xsa/advisory-410.html
mitigation, patch, vendor-advisory
-
openwall.com
/lists/oss-security/2022/10/11/3
mailing-list, mitigation, patch, third-party-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/XWSC77GS5NATI3TT7FMVPULUPXR635XQ/
vendor-advisory
-
debian.org
/security/2022/dsa-5272
vendor-advisory, third-party-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/TJOMUNGW6VTK5CZZRLWLVVEOUPEQBRHI/
vendor-advisory
-
lists.fedoraproject.org
/archives/list/package-announce%40lists.fedoraproject.org/message/YZVXG7OOOXCX6VIPEMLFDPIPUTFAYWPE/
vendor-advisory
-
security.gentoo.org
/glsa/202402-07
vendor-advisory
Sources
- CVE List CVE-2022-33746
- NVD CVE-2022-33746
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.