https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Thu, 01 Oct 2026 00:27:13 +0000 https://vulnerability.circl.lu/vuln/cve-2026-74514 <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: s390: pci: Fix memory accounting for pinned/unpinned pages</p> <p>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&#39;t decrement the count by calling free_uid(). It also accounted/unaccounted the pages against the current-&gt;mm. But its possible the unaccount_mem() can be called from a different process context than the one that originally pinned the pages.</p> <p>Let&#39;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.</p> <p>[borntraeger@linux.ibm.com: Fixed whitespace]</p> <p><strong>Affected:</strong> Linux</p> <p>In the Linux kernel, the following vulnerability has been resolved:</p> <p>KVM: s390: pci: Fix memory accounting for pinned/unpinned pages</p> <p>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&#39;t decrement the count by calling free_uid(). It also accounted/unaccounted the pages against the current-&gt;mm. But its possible the unaccount_mem() can be called from a different process context than the one that originally pinned the pages.</p> <p>Let&#39;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.</p> <p>[borntraeger@linux.ibm.com: Fixed whitespace]</p> https://vulnerability.circl.lu/vuln/cve-2026-74514