Skip to content
CVE Ledger
  • Newest CVEsPage
  • Recently added to KEVPage
  • Rising exploitation (EPSS)Page
  • Weekly digestPage
  • StatisticsPage
  • WatchlistPage
  • API docsPage
  • MCP serverPage
  • AboutPage
  • Data sourcesPage
  • Data statusPage
  • ChangelogPage
  • How it's builtPage
  • Support the projectPage

14 results

Back

CVE-2026-74514KVM: s390: pci: Fix memory accounting for pinned/unpinned pages

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]

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 8 days later

    Record updated

Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.

Scores

No CVSS score yet: neither the CNA, CISA nor NVD has scored this CVE. NVD status: Received.

EPSS (exploitation in 30 days)
0.17% · top 93% of all CVEs (18 Nov 2026)
Loading the EPSS history…

The list uses the assigner's score when there is one, then CISA's, then NVD's: Not scored.

Affected products

  • Linux · Linux

    • affected 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc – < ad1c2ac7f15b224cf9ab26b593caa9bd1a4be72e
    • affected 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc – < dc7465a364104526c56b922c9de9dfcc08a7d5f7
    • affected 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc – < 47cfd75d9df7c8f425b0d769328fe43a8a8e606e
    • affected 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc – < 70871b121f81d08879363cb1238a4c85c5c2800c
    • affected 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc – < e3f732e086e438c52c7400bd2734bb166aa4752c
    • affected 3c5a1b6f0a18520a0edd0600fef6f1a8553b8fdc – < 36f6999ecde3976731a8bfc0b8e667da6f593069
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.1.184 – ≤ 6.1.*
    • unaffected 6.6.152 – ≤ 6.6.*
    • unaffected 6.12.104 – ≤ 6.12.*
    • unaffected 6.18.44 – ≤ 6.18.*
    • unaffected 7.1.8 – ≤ 7.1.*
    • unaffected 7.2 – ≤ *

References

References6

Sources

The same CVE in the primary databases and aggregators, to check against.

Badge for a README or a ticket

CVE-2026-74514 badge
[![CVE-2026-74514](https://cveledger.app/badge/CVE-2026-74514.svg)](https://cveledger.app/cve/CVE-2026-74514)

Record last updated .