CVE-2026-74514

KVM: s390: pci: Fix memory accounting for pinned/unpinned pages

N/A
Published: August 15, 2026 at 12:27 PM UTC
Updated: August 23, 2026 at 01:17 PM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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. [[email protected]: Fixed whitespace]

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.0 ≤ v < 6.1.1846.0 ≤ v < 6.12.1046.0 ≤ v < 6.18.446.0 ≤ v < 6.6.1526.0 ≤ v < 7.1.86.0 ≤ v < 7.23c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc6.0
Vendor states this is fixed in 36f6999ecde3976731a8bfc0b8e667da6f593069 (fixed)
Vendor states this is fixed in 47cfd75d9df7c8f425b0d769328fe43a8a8e606e (fixed)
Vendor states this is fixed in 70871b121f81d08879363cb1238a4c85c5c2800c (fixed)
Vendor states this is fixed in ad1c2ac7f15b224cf9ab26b593caa9bd1a4be72e (fixed)
Vendor states this is fixed in dc7465a364104526c56b922c9de9dfcc08a7d5f7 (fixed)
Vendor states this is fixed in e3f732e086e438c52c7400bd2734bb166aa4752c (fixed)
Vendor states this is fixed in 6.0 (unaffected)
Vendor states this is fixed in 6.1.184 (unaffected)
Vendor states this is fixed in 6.12.104 (unaffected)
Vendor states this is fixed in 6.18.44 (unaffected)
Vendor states this is fixed in 6.6.152 (unaffected)
Vendor states this is fixed in 7.1.8 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card