Vulnerability · Published Jun 18, 2025 · Assigned by Linux
CVE-2022-49989xen/privcmd: fix error exit of privcmd_ioctl_dm_op()
Medium 5.5
In plain English
A medium-severity security flaw in Linux from Linux. There are no confirmed reports of exploitation so far. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 17% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.
Official description
In the Linux kernel, the following vulnerability has been resolved: xen/privcmd: fix error exit of privcmd_ioctl_dm_op() The error exit of privcmd_ioctl_dm_op() is calling unlock_pages() potentially with pages being NULL, leading to a NULL dereference. Additionally lock_pages() doesn't check for pin_user_pages_fast() having been completely successful, resulting in potentially not locking all pages into memory. This could result in sporadic failures when using the related memory in user mode. Fix all of that by calling unlock_pages() always with the real number of pinned pages, which will be zero in case pages being NULL, and by checking the number of pages pinned by pin_user_pages_fast() matching the expected number of pages.
Affected packages & fixed versions
| Ecosystem | Package | Fixed in | Advisory |
|---|---|---|---|
| Debian:12 | linux | 6.0.2-1 | DEBIAN-CVE-2022-49989 |
| Debian:13 | linux | 6.0.2-1 | DEBIAN-CVE-2022-49989 |
| Debian:14 | linux | 6.0.2-1 | DEBIAN-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux | 5.15.0-53.59 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-allwinner-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-aws | 5.15.0-1023.27 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-aws-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-aws-6.2 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-aws-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-azure | 5.15.0-1023.29 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-azure-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-azure-6.2 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-azure-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-azure-fde | 5.15.0-1024.30.1 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-azure-fde-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-azure-fde-6.2 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-gcp | 5.15.0-1022.29 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-gcp-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-gcp-6.2 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-gcp-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-gke | 5.15.0-1020.25 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-gkeop | 5.15.0-1008.12 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-ibm | 5.15.0-1018.21 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-intel-iot-realtime | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-intel-iotg | 5.15.0-1018.23 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-kvm | 5.15.0-1021.26 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-lowlatency | 5.15.0-53.59 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.2 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-lowlatency-hwe-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-nvidia | 5.15.0-1015.15 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-nvidia-6.2 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-nvidia-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-oem-5.17 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-oem-6.0 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-oem-6.1 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-oem-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-oracle | 5.15.0-1022.28 | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-oracle-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-raspi | 5.15.0-1018.20 | UBUNTU-CVE-2022-49989 |
| Ubuntu:24.04:LTS | linux-raspi-realtime | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:24.04:LTS | linux-realtime | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:24.04:LTS | linux-riscv | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-riscv-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-riscv-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-starfive-5.19 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-starfive-6.2 | no fix listed | UBUNTU-CVE-2022-49989 |
| Ubuntu:22.04:LTS | linux-starfive-6.5 | no fix listed | UBUNTU-CVE-2022-49989 |
Affected products (as reported)
| Vendor | Product | Versions |
|---|---|---|
| Linux | Linux | ab520be8cd5d56867fc95cfbc34b90880faf1f9d – before 6de50db104af0dc921f593fd95c55db86a52ceefab520be8cd5d56867fc95cfbc34b90880faf1f9d – before c2b7bae7c90051fd6a679d5dee00400d67ebbf4aab520be8cd5d56867fc95cfbc34b90880faf1f9d – before 45d47bd9b96e7874b98dbcc7602fe2826c5d62a6ab520be8cd5d56867fc95cfbc34b90880faf1f9d – before c5deb27895e017a0267de0a20d140ad5fcc55a54 |
| Linux | Linux | 4.11 |