CVE-2025-58144
published 2025-09-11CVE-2025-58144: [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] There are two issues related…
PriorityP339high7.5CVSS 3.1
AVNACLPRNUINSUCNINAH
EPSS
0.42%
34.0th percentile
[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]
There are two issues related to the mapping of pages belonging to other
domains: For one, an assertion is wrong there, where the case actually
needs handling. A NULL pointer de-reference could result on a release
build. This is CVE-2025-58144.
And then the P2M lock isn't held until a page reference was actually
obtained (or the attempt to do so has failed). Otherwise the page can
not only change type, but even ownership in between, thus allowing
domain boundaries to be violated. This is CVE-2025-58145.
Affected
10 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | xen | < xen 4.17.5+72-g01140da4e8-1 (bookworm) | xen 4.17.5+72-g01140da4e8-1 (bookworm) |
| xen | xen | >= 0 < 4.18.5-r2 | 4.18.5-r2 |
| xen | xen | >= 0 < 4.18.5-r2 | 4.18.5-r2 |
| xen | xen | >= 0 < 4.19.3-r1 | 4.19.3-r1 |
| xen | xen | >= 0 < 4.20.1-r1 | 4.20.1-r1 |
| xen | xen | >= 0 < 4.20.1-r1 | 4.20.1-r1 |
| xen | xen | >= 0 < 4.17.5+72-g01140da4e8-1 | 4.17.5+72-g01140da4e8-1 |
| xen | xen | >= 0 < 4.20.2+7-g1badcf5035-0+deb13u1 | 4.20.2+7-g1badcf5035-0+deb13u1 |
| xen | xen | >= 0 < 4.20.2+7-g1badcf5035-1 | 4.20.2+7-g1badcf5035-1 |
| xen | xen | >= 4.12.0 < 4.17.0 | 4.17.0 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
osv7.5HIGH
vendor_debian7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2025-58144: [This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE
osv·2025-09-11·CVSS 7.5
CVE-2025-58144 [HIGH] CVE-2025-58144: [This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE
[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]
There are two issues related to the mapping of pages belonging to other
domains: For one, an assertion is wrong there, where the case actually
needs handling. A NULL pointer de-reference could result on a release
build. This is CVE-2025-58144.
And then the P2M lock isn't held until a page reference was actually
obtained (or the attempt to do so has failed). Otherwise the page can
not only change type, but even ownership in between, thus allowing
domain boundaries to be violated. This is CVE-2025-58145.
OSV
CVE-2025-58145: [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE
osv·2025-09-11·CVSS 7.5
CVE-2025-58145 [HIGH] CVE-2025-58145: [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] There are two issues related to the mapping of pages belonging to other domains: For one, an assertion is wrong there, where the case actually needs handling. A NULL pointer de-reference could result on a release build. This is CVE-2025-58144. And then the P2M lock isn't held until a page reference was actually obtained (or the attempt to do so has failed). Otherwise the page can not only change type, but even ownership in between, thus allowing domain boundaries to be violated. This is CVE-2025-58145.
GHSA
GHSA-4433-h798-3mr7: [This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE
ghsa_unreviewed·2025-09-11·CVSS 7.5
CVE-2025-58144 [HIGH] CWE-476 GHSA-4433-h798-3mr7: [This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE
[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]
There are two issues related to the mapping of pages belonging to other
domains: For one, an assertion is wrong there, where the case actually
needs handling. A NULL pointer de-reference could result on a release
build. This is CVE-2025-58144.
And then the P2M lock isn't held until a page reference was actually
obtained (or the attempt to do so has failed). Otherwise the page can
not only change type, but even ownership in between, thus allowing
domain boundaries to be violated. This is CVE-2025-58145.
OSV
CVE-2025-58145: [This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE
osv·2025-09-11·CVSS 7.5
CVE-2025-58145 [HIGH] CVE-2025-58145: [This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE
[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]
There are two issues related to the mapping of pages belonging to other
domains: For one, an assertion is wrong there, where the case actually
needs handling. A NULL pointer de-reference could result on a release
build. This is CVE-2025-58144.
And then the P2M lock isn't held until a page reference was actually
obtained (or the attempt to do so has failed). Otherwise the page can
not only change type, but even ownership in between, thus allowing
domain boundaries to be violated. This is CVE-2025-58145.
GHSA
GHSA-j9v5-p5pj-rmp7: [This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE
ghsa_unreviewed·2025-09-11·CVSS 7.5
CVE-2025-58145 [HIGH] CWE-362 GHSA-j9v5-p5pj-rmp7: [This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE
[This CNA information record relates to multiple CVEs; the
text explains which aspects/vulnerabilities correspond to which CVE.]
There are two issues related to the mapping of pages belonging to other
domains: For one, an assertion is wrong there, where the case actually
needs handling. A NULL pointer de-reference could result on a release
build. This is CVE-2025-58144.
And then the P2M lock isn't held until a page reference was actually
obtained (or the attempt to do so has failed). Otherwise the page can
not only change type, but even ownership in between, thus allowing
domain boundaries to be violated. This is CVE-2025-58145.
OSV
CVE-2025-58144: [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE
osv·2025-09-11·CVSS 7.5
CVE-2025-58144 [HIGH] CVE-2025-58144: [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] There are two issues related to the mapping of pages belonging to other domains: For one, an assertion is wrong there, where the case actually needs handling. A NULL pointer de-reference could result on a release build. This is CVE-2025-58144. And then the P2M lock isn't held until a page reference was actually obtained (or the attempt to do so has failed). Otherwise the page can not only change type, but even ownership in between, thus allowing domain boundaries to be violated. This is CVE-2025-58145.
Debian
CVE-2025-58145: xen - [This CNA information record relates to multiple CVEs; the text explains which a...
vendor_debian·2025·CVSS 7.5
CVE-2025-58145 [HIGH] CVE-2025-58145: xen - [This CNA information record relates to multiple CVEs; the text explains which a...
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] There are two issues related to the mapping of pages belonging to other domains: For one, an assertion is wrong there, where the case actually needs handling. A NULL pointer de-reference could result on a release build. This is CVE-2025-58144. And then the P2M lock isn't held until a page reference was actually obtained (or the attempt to do so has failed). Otherwise the page can not only change type, but even ownership in between, thus allowing domain boundaries to be violated. This is CVE-2025-58145.
Scope: local
bookworm: resolved (fixed in 4.17.5+72-g01140da4e8-1)
bullseye: open
forky: resolved (fixed in 4.20.2+7-g1badcf5035-1)
sid: resolved (fixed in 4.20.2+
Debian
CVE-2025-58144: xen - [This CNA information record relates to multiple CVEs; the text explains which a...
vendor_debian·2025·CVSS 7.5
CVE-2025-58144 [HIGH] CVE-2025-58144: xen - [This CNA information record relates to multiple CVEs; the text explains which a...
[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] There are two issues related to the mapping of pages belonging to other domains: For one, an assertion is wrong there, where the case actually needs handling. A NULL pointer de-reference could result on a release build. This is CVE-2025-58144. And then the P2M lock isn't held until a page reference was actually obtained (or the attempt to do so has failed). Otherwise the page can not only change type, but even ownership in between, thus allowing domain boundaries to be violated. This is CVE-2025-58145.
Scope: local
bookworm: resolved (fixed in 4.17.5+72-g01140da4e8-1)
bullseye: open
forky: resolved (fixed in 4.20.2+7-g1badcf5035-1)
sid: resolved (fixed in 4.20.2+
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
2025-09-11
Published