KVM: s390: pci: Fix memory accounting for pinned/unpinned pages
Linux
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
Linux
| Product | Affected | Fixed in |
|---|---|---|
| Linux Linux |
|
≥ 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc · < 36f6999ecde3976731a8bfc0b8e667da6f593069| No fix yet |
| Linux Linux |
|
|
In the Linux kernel, the following vulnerability has been resolved:
KVM: s390: pci: Fix memory accounting for pinned/unpinned pages
The account_mem() and unaccount_mem() functions call get_uid() which increments the reference count of struct user_struct on every invocation. But we don't decrement the count by calling free_uid(). It also accounted/unaccounted the pages against the current->mm. But its possible the unaccount_mem() can be called from a different process context than the one that originally pinned the pages.
Let's fix this by storing the pinning process user_struct and mm_struct when accounting for pinned pages, and subsequently free these resources when the pages are unpinned.
[borntraeger@linux.ibm.com: Fixed whitespace]
From the CVE record · Linux
The Linux kernel's KVM s390 PCI code leaks user-structure references when accounting for pinned pages. It can also charge unpinned pages to the wrong process if unpinning happens in a different process context. The input does not specify an attack path or authentication requirements.
Engineers running Linux kernels with KVM s390 PCI support should check their kernel; affected versions are not specified.