CVE-2026-74514: KVM: s390: pci: Fix memory accounting for pinned/unpinned pages
Noroxi assessment
Priority: Monitor (action score 0/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.17% (FIRST EPSS).
- Fixed version: Linux Linux 36f6999ecde3976731a8bfc0b8e667da6f593069, 47cfd75d9df7c8f425b0d769328fe43a8a8e606e, 70871b121f81d08879363cb1238a4c85c5c2800c.
- Mentioned 2 times in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 36f6999ecde3976731a8bfc0b8e667da6f593069, 47cfd75d9df7c8f425b0d769328fe43a8a8e606e, 70871b121f81d08879363cb1238a4c85c5c2800c or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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]
- Published
- Aug 15, 2026
- Updated
- Aug 23, 2026
- EPSS
- 0.1% · 6th percentile
- CWE
- —
Report tools
Action score
0
Monitor
Low priority for now.
- CVSS
- 0 / 40 · —
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Linux). Independent of NVD's CPE analysis and usually ahead of it.
Linux Linux
- 6.0affected
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before ad1c2ac7f15b224cf9ab26b593caa9bd1a4be72eaffected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before dc7465a364104526c56b922c9de9dfcc08a7d5f7affected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before 47cfd75d9df7c8f425b0d769328fe43a8a8e606eaffected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before 70871b121f81d08879363cb1238a4c85c5c2800caffected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before e3f732e086e438c52c7400bd2734bb166aa4752caffected · git
- 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc and later · before 36f6999ecde3976731a8bfc0b8e667da6f593069affected · git
- before 6.0not affected · semver
- 6.1.184 and later · up to and including 6.1.*not affected · semver
- 6.6.152 and later · up to and including 6.6.*not affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | linux | before 6.1.187-1 | 6.1.187-1 |
| Debian:12 | linux-6.12 | before 6.12.107-1~deb12u1 | 6.12.107-1~deb12u1 |
| Debian:13 | linux | before 6.12.105-1 | 6.12.105-1 |
| Debian:14 | linux | before 7.1.8-1 | 7.1.8-1 |
Same product
linux: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-74705udp: fix potential use-after-free in tunnel segmentation40Plan
- CVE-2026-74612veth: fix skb length accounting after XDP frag adjustment40Plan
- CVE-2026-74475vxlan: use neigh_ha_snapshot() in route_shortcircuit()40Plan
Published before and after this one in the same product
- ← EarlierCVE-2026-74502Aug 15, 2026 · ALSA: ump: fix double free of out_cvts on rawmidi error0Monitor
- ← EarlierCVE-2026-74504Aug 15, 2026 · ALSA: seq: Fix division by zero in initialize_timer()0Monitor
- Later →CVE-2026-74522Aug 15, 2026 · ksmbd: fix use-after-free in __close_file_table_ids()35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Linux Linux | 36f6999ecde3976731a8bfc0b8e667da6f593069 | Vendor (CNA) |
| Linux Linux | 47cfd75d9df7c8f425b0d769328fe43a8a8e606e | Vendor (CNA) |
| Linux Linux | 70871b121f81d08879363cb1238a4c85c5c2800c | Vendor (CNA) |
| Linux Linux | ad1c2ac7f15b224cf9ab26b593caa9bd1a4be72e | Vendor (CNA) |
| Linux Linux | dc7465a364104526c56b922c9de9dfcc08a7d5f7 | Vendor (CNA) |
| Linux Linux | e3f732e086e438c52c7400bd2734bb166aa4752c | Vendor (CNA) |
| debian:linux | 6.1.187-1 · Debian:12 | Package registry (OSV) |
| debian:linux-6.12 | 6.12.107-1~deb12u1 · Debian:12 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
National notice (Türkiye Cybersecurity Directorate / USOM)
Official security notices citing this record; remediation advice is on the agency's page.
- TR-26-0860 · Aug 19, 2026(IBM Db2 Mirror Güvenlik Bildirimi)
- TR-26-0854 · Aug 19, 2026(Linux Kernel Güvenlik Bildirimi)
Technical details
No CVSS vector for this record, so attack conditions can't be derived.
Weakness class (CWE)
—
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
- git.kernel.org/stable/c/47cfd75d9df7c8f425b0d769328fe43a8a8e606e
- git.kernel.org/stable/c/70871b121f81d08879363cb1238a4c85c5c2800c
- git.kernel.org/stable/c/ad1c2ac7f15b224cf9ab26b593caa9bd1a4be72e
- git.kernel.org/stable/c/dc7465a364104526c56b922c9de9dfcc08a7d5f7
- git.kernel.org/stable/c/e3f732e086e438c52c7400bd2734bb166aa4752c
Vendor advisories and official records. Exploit/PoC links are deliberately left out.