Your message dated Fri, 05 Dec 2025 16:03:35 +0000
with message-id <[email protected]>
and subject line Bug#1120075: fixed in xen 4.17.5+72-g01140da4e8-1
has caused the Debian Bug report #1120075,
regarding xen: CVE-2025-27465 CVE-2025-27466 CVE-2025-58142 CVE-2025-58143
CVE-2025-58144 CVE-2025-58145 CVE-2025-58147 CVE-2025-58148 CVE-2025-58149
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1120075: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1120075
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: xen
Version: 4.20.0+68-g35cb38b222-1
Severity: grave
Tags: security upstream
Justification: user security hole
X-Debbugs-Cc: [email protected], Debian Security Team <[email protected]>
Hi,
The following vulnerabilities were published for xen.
CVE-2025-27465[0]:
| Certain instructions need intercepting and emulating by Xen. In
| some cases Xen emulates the instruction by replaying it, using an
| executable stub. Some instructions may raise an exception, which is
| supposed to be handled gracefully. Certain replayed instructions
| have additional logic to set up and recover the changes to the
| arithmetic flags. For replayed instructions where the flags
| recovery logic is used, the metadata for exception handling was
| incorrect, preventing Xen from handling the the exception
| gracefully, treating it as fatal instead.
CVE-2025-27466[1]:
| [This CNA information record relates to multiple CVEs; the text
| explains which aspects/vulnerabilities correspond to which CVE.]
| There are multiple issues related to the handling and accessing of
| guest memory pages in the viridian code: 1. A NULL pointer
| dereference in the updating of the reference TSC area. This is
| CVE-2025-27466. 2. A NULL pointer dereference by assuming the SIM
| page is mapped when a synthetic timer message has to be
| delivered. This is CVE-2025-58142. 3. A race in the mapping
| of the reference TSC page, where a guest can get Xen to free a
| page while still present in the guest physical to machine (p2m)
| page tables. This is CVE-2025-58143.
CVE-2025-58142[2]:
| [This CNA information record relates to multiple CVEs; the text
| explains which aspects/vulnerabilities correspond to which CVE.]
| There are multiple issues related to the handling and accessing of
| guest memory pages in the viridian code: 1. A NULL pointer
| dereference in the updating of the reference TSC area. This is
| CVE-2025-27466. 2. A NULL pointer dereference by assuming the SIM
| page is mapped when a synthetic timer message has to be
| delivered. This is CVE-2025-58142. 3. A race in the mapping
| of the reference TSC page, where a guest can get Xen to free a
| page while still present in the guest physical to machine (p2m)
| page tables. This is CVE-2025-58143.
CVE-2025-58143[3]:
| [This CNA information record relates to multiple CVEs; the text
| explains which aspects/vulnerabilities correspond to which CVE.]
| There are multiple issues related to the handling and accessing of
| guest memory pages in the viridian code: 1. A NULL pointer
| dereference in the updating of the reference TSC area. This is
| CVE-2025-27466. 2. A NULL pointer dereference by assuming the SIM
| page is mapped when a synthetic timer message has to be
| delivered. This is CVE-2025-58142. 3. A race in the mapping
| of the reference TSC page, where a guest can get Xen to free a
| page while still present in the guest physical to machine (p2m)
| page tables. This is CVE-2025-58143.
CVE-2025-58144[4]:
| [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.
CVE-2025-58145[5]:
| [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.
CVE-2025-58147[6]:
| [This CNA information record relates to multiple CVEs; the text
| explains which aspects/vulnerabilities correspond to which CVE.]
| Some Viridian hypercalls can specify a mask of vCPU IDs as an input,
| in one of three formats. Xen has boundary checking bugs with all
| three formats, which can cause out-of-bounds reads and writes while
| processing the inputs. * CVE-2025-58147. Hypercalls using the
| HV_VP_SET Sparse format can cause vpmask_set() to write out of
| bounds when converting the bitmap to Xen's format. *
| CVE-2025-58148. Hypercalls using any input format can cause
| send_ipi() to read d->vcpu[] out-of-bounds, and operate on a wild
| vCPU pointer.
CVE-2025-58148[7]:
| [This CNA information record relates to multiple CVEs; the text
| explains which aspects/vulnerabilities correspond to which CVE.]
| Some Viridian hypercalls can specify a mask of vCPU IDs as an input,
| in one of three formats. Xen has boundary checking bugs with all
| three formats, which can cause out-of-bounds reads and writes while
| processing the inputs. * CVE-2025-58147. Hypercalls using the
| HV_VP_SET Sparse format can cause vpmask_set() to write out of
| bounds when converting the bitmap to Xen's format. *
| CVE-2025-58148. Hypercalls using any input format can cause
| send_ipi() to read d->vcpu[] out-of-bounds, and operate on a wild
| vCPU pointer.
CVE-2025-58149[8]:
| When passing through PCI devices, the detach logic in libxl won't
| remove access permissions to any 64bit memory BARs the device might
| have. As a result a domain can still have access any 64bit memory
| BAR when such device is no longer assigned to the domain. For PV
| domains the permission leak allows the domain itself to map the
| memory in the page-tables. For HVM it would require a compromised
| device model or stubdomain to map the leaked memory into the HVM
| domain p2m.
If you fix the vulnerabilities please also make sure to include the
CVE (Common Vulnerabilities & Exposures) ids in your changelog entry.
For further information see:
[0] https://security-tracker.debian.org/tracker/CVE-2025-27465
https://www.cve.org/CVERecord?id=CVE-2025-27465
[1] https://security-tracker.debian.org/tracker/CVE-2025-27466
https://www.cve.org/CVERecord?id=CVE-2025-27466
[2] https://security-tracker.debian.org/tracker/CVE-2025-58142
https://www.cve.org/CVERecord?id=CVE-2025-58142
[3] https://security-tracker.debian.org/tracker/CVE-2025-58143
https://www.cve.org/CVERecord?id=CVE-2025-58143
[4] https://security-tracker.debian.org/tracker/CVE-2025-58144
https://www.cve.org/CVERecord?id=CVE-2025-58144
[5] https://security-tracker.debian.org/tracker/CVE-2025-58145
https://www.cve.org/CVERecord?id=CVE-2025-58145
[6] https://security-tracker.debian.org/tracker/CVE-2025-58147
https://www.cve.org/CVERecord?id=CVE-2025-58147
[7] https://security-tracker.debian.org/tracker/CVE-2025-58148
https://www.cve.org/CVERecord?id=CVE-2025-58148
[8] https://security-tracker.debian.org/tracker/CVE-2025-58149
https://www.cve.org/CVERecord?id=CVE-2025-58149
Regards,
Salvatore
--- End Message ---
--- Begin Message ---
Source: xen
Source-Version: 4.17.5+72-g01140da4e8-1
Done: Hans van Kranenburg <[email protected]>
We believe that the bug you reported is fixed in the latest version of
xen, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Hans van Kranenburg <[email protected]> (supplier of updated xen package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 29 Nov 2025 14:52:25 +0100
Source: xen
Architecture: source
Version: 4.17.5+72-g01140da4e8-1
Distribution: bookworm-security
Urgency: medium
Maintainer: Debian Xen Team <[email protected]>
Changed-By: Hans van Kranenburg <[email protected]>
Closes: 1092495 1105193 1105222 1120075
Changes:
xen (4.17.5+72-g01140da4e8-1) bookworm-security; urgency=medium
.
Significant changes:
* Update to new upstream version 4.17.5+72-g01140da4e8, which also contains
security fixes for the following issues:
(Closes: #1105193) (Closes: #1120075)
- deadlock potential with VT-d and legacy PCI device pass-through
XSA-467 CVE-2025-1713
- x86: Indirect Target Selection
XSA-469 CVE-2024-28956
- x86: Incorrect stubs exception handling for flags recovery
XSA-470 CVE-2025-27465
- x86: Transitive Scheduler Attacks
XSA-471 CVE-2024-36350 CVE-2024-36357
- Multiple vulnerabilities in the Viridian interface
XSA-472 CVE-2025-27466 CVE-2025-58142 CVE-2025-58143
- Arm issues with page refcounting
XSA-473 CVE-2025-58144 CVE-2025-58145
- x86: Incorrect input sanitisation in Viridian hypercalls
XSA-475 CVE-2025-58147 CVE-2025-58148
- Incorrect removal of permissions on PCI device unplug
XSA-476 CVE-2025-58149
* Note that the following XSA are not listed, because...
- XSA-468 applies to Windows PV drivers
- XSA-474 applies to XAPI which is not included in Debian
.
Packaging minor fixes and improvements:
* debian/salsa-ci.yml: adjust for new salsa-ci pipeline
.
Additional changes for 4.17 that were not backported upstream:
* Cherry-pick dd05d265b8 ("x86/intel: Fix PERF_GLOBAL fixup when
virtualised") to fix a boot loop when using Xen under nested
virtualization (Closes: #1105222)
.
xen (4.17.5+23-ga4e5191dc0-1+deb12u1) bookworm; urgency=medium
.
* Ignore lintian error not relevant for bookworm in salsa-ci.
* Cherry-pick e6472d4668 (tools/xg: increase LZMA_BLOCK_SIZE for
uncompressing the kernel) to allow direct kernel boot with kernels >=
6.12 (Closes: #1092495).
Checksums-Sha1:
d03ef7857b919f4bedeccc2cad4e8653edc2e54a 4357 xen_4.17.5+72-g01140da4e8-1.dsc
484aee73ee641a79784ccca082d88548f1979258 4735560
xen_4.17.5+72-g01140da4e8.orig.tar.xz
d4cd8a6ea02d46f176911e307579dc706445215b 139916
xen_4.17.5+72-g01140da4e8-1.debian.tar.xz
Checksums-Sha256:
f13956b67fb7a65707c2b0620d89b41ee5d203434dd7bb913017356791ee66c1 4357
xen_4.17.5+72-g01140da4e8-1.dsc
53922f4d0a02c577f2ea9d63f65989cd88715779eebeed879ca1d314103ee06e 4735560
xen_4.17.5+72-g01140da4e8.orig.tar.xz
5bcf3812c64585e270e0b3fa6ee8fd16dff7b9bc0f61375d648c64672484c4d9 139916
xen_4.17.5+72-g01140da4e8-1.debian.tar.xz
Files:
cc505f0bae1df37fc71190cece7ef8c6 4357 admin optional
xen_4.17.5+72-g01140da4e8-1.dsc
a06455fe8e2cb343077c1160dcbb542d 4735560 admin optional
xen_4.17.5+72-g01140da4e8.orig.tar.xz
0cc6fc105905d9e93bd1a9bc6ebac890 139916 admin optional
xen_4.17.5+72-g01140da4e8-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEtuYvPRKsOElcDakFEMKTtsN8TjYFAmku1R8ACgkQEMKTtsN8
Tja3WhAAmClBrRJmNE9WkWcdjxCTkOt4keVmN1KCwF5AWgV6f6xzT5HXD1JuG9jY
lNTuaXOcUsAaOn8aLiCWl0+42U0bQMWWYIPP/4V5yBVod1WMl4muGl+nSr/y0+xs
87TGQ97bEgyvhKGVoYeTG9ypXwB/5nACpVkSi4SZs5c2ZNMCSB2SrDSv2CCexmFW
0ZGOGgeAXDYT/2/1OEbJ48ksvnAue2uaZx3HiD3wx1w8vczHKYWABDOMXNrOUR8/
V3pYw3IpdrM8EoUnfW8QXblTDuzIqHZthVyn3dDfO/KV25/DMl+g+oqL3CXlS6/K
WblGxF3o/sy3KWB6yFDaPQ9H5X4TktreM+DJFAETYmHtZavD4MC7vyKqBxreoF6A
8Y6jtqa0+bgRd5xm4OSrKHhNQXzUE/5HZK+TQiznvc4wIAzzNY7JUuctGHji6Ugk
Uh+J3K1tK8TwiDNiB5Qcwh+reAm68o5aIO8zgvvUDYodyo0hitVpo2V4Pj62JGKL
UpwPGZNu7zfgEaXi8ZOkOnX+v35fBItI9cPe7Yd9zi8RSVqI03k83Jv5+Lq/0R0h
/HmeYAMuJo5BI5islx540orIm9UvzxwqxdoVmF0GUo7uIK2X0PxpvPQiFKfJsPDq
lvJotSsLT1TZpYsOSa6JJWVOnyMeQkjrjIqEk8DaKwK7SBV06yY=
=CISm
-----END PGP SIGNATURE-----
pgpI2oPAhTf6I.pgp
Description: PGP signature
--- End Message ---
