xen/privcmd: fix error exit of privcmd_ioctl_dm_op()
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
| No fix yet |
| Linux Linux |
|
|
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.
From the CVE record · Linux
The Linux kernel’s privcmd_ioctl_dm_op() error path can dereference a NULL pages pointer. A local user invoking the affected ioctl could trigger this error path; incomplete page pinning can also cause sporadic failures when the related memory is used in user mode.
Engineers running Linux kernels with xen/privcmd should check their kernel versions against the vendor advisory; affected versions were not provided.