Skip to main content
cve.nowby Sazabi
← All vulnerabilities
CVE-2026-31788

xen/privcmd: restrict usage in unprivileged domU

Published
Last modified
published
Not listed in CISA KEV
Fix
Fixed in 5.10.253, 5.15.203, 6.1.167, 6.6.130, 6.12.78, and 2 more
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: restrict usage in unprivileged domU The Xen privcmd driver allows to issue arbitrary hypercalls from user space processes. This is normally no problem, as access is usually limited to root and the hypervisor will deny any hypercalls affecting other domains. In case the guest is booted using secure boot, however, the privcmd driver would be enabling a root user process to modify e.g. kernel memory contents, thus breaking the secure boot feature. The only known case where an unprivileged domU is really needing to use the privcmd driver is the case when it is acting as the device model for another guest. In this case all hypercalls issued via the privcmd driver will target that other guest. Fortunately the privcmd driver can already be locked down to allow only hypercalls targeting a specific domain, but this mode can be activated from user land only today. The target domain can be obtained from Xenstore, so when not running in dom0 restrict the privcmd driver to that target domain from the beginning, resolving the potential problem of breaking secure boot. This is XSA-482 --- V2: • defer reading from Xenstore if Xenstore isn't ready yet (Jan Beulich) • wait in open() if target domain isn't known yet • issue message in case no target domain found (Jan Beulich)

Timeline

  1. CVE published
  2. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  3. Record last updated

Affected versions

  • Linux Linux

    From 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b · fixed in 4eb245ff0d33b618e097a2c23de5df56d4ad6969; From 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b · fixed in 3ee5b9e3de4b8bdd74183d83205481c91a9effc8; From 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b · fixed in 87a803edb2ded911cb587c53bff179d2a2ed2a28; From 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b · fixed in 1879319d790f7d57622cdc22807b60ea78b56b6d; From 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b · fixed in 78432d8f0372c71c518096395537fa12be7ff24e; From 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b · fixed in 389bae9a4409934e8b8d4dbdaaf02a3ae71cf8e4; From 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b · fixed in cbede2e833da1893afbea9b3ff29b5dda23a4a91; From 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b · fixed in 453b8fb68f3641fea970db88b7d9a153ed2a37e8

  • Linux Linux

    2.6.37

  • KernelLinux

    From 2.6.37 · fixed in 5.10.253; From 5.11.0 · fixed in 5.15.203; From 5.16.0 · fixed in 6.1.167; From 6.2.0 · fixed in 6.6.130; From 6.7.0 · fixed in 6.12.78; From 6.13.0 · fixed in 6.18.20; From 6.19.0 · fixed in 6.19.10

References 8

git.kernel.org