CVE-2026-31788High· 8.2▾ TwilightIn 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…
▾ Twilight zone — High severity, or a signal on a lesser flaw
impact 45.1 · likelihood 0 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Stakeholder-Specific Vulnerability Categorization from CISA's ADP record at CVE.org: whether exploitation is observed, whether an attack can be automated, and how much of the system is at stake. The CVSS score shown above comes from the assigning CNA record, not NVD.
Exploit-prediction probability, daily snapshots since Oct 16.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via CVEORG
0.2%
Last analysed / modified upstream
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:
Linux >= 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b < 4eb245ff0d33b618e097a2c23de5df56d4ad6969Linux >= 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b < 3ee5b9e3de4b8bdd74183d83205481c91a9effc8Linux >= 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b < 87a803edb2ded911cb587c53bff179d2a2ed2a28Linux >= 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b < 1879319d790f7d57622cdc22807b60ea78b56b6dLinux >= 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b < 78432d8f0372c71c518096395537fa12be7ff24eLinux >= 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b < 389bae9a4409934e8b8d4dbdaaf02a3ae71cf8e4Linux >= 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b < cbede2e833da1893afbea9b3ff29b5dda23a4a91Linux >= 1c5de1939c204bde9cce87f4eb3d26e9f9eb732b < 453b8fb68f3641fea970db88b7d9a153ed2a37e8Linux 2.6.37Refer to the linked advisories for vendor-supplied fixes and affected version ranges.
Connected by shared product, vendor, weakness, or advisory.
CVE-2026-99118Nonedrm/i915/dmc: Harden DMC firmware payload parsing
CVE-2026-99117Nonenet: bridge: mcast: don't truncate the port group walk on teardown
CVE-2026-99121Noneipv4: avoid divide by zero in fib_rebalance
CVE-2026-99120NoneKVM: x86/mmu: Cope with the SS bit being set in #NPF exit codes
CVE-2026-99119Nonedrm/amdgpu/userq: actually validate userq BOs
CVE-2026-99123Nonevsock/virtio: validate packet source for connected sockets