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-98003iommu/amd: Do not reallocate GA log buffers on resume

Description

In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Do not reallocate GA log buffers on resume Commit c5e1a1eb9279 ("iommu/amd: Simplify and Consolidate Virtual APIC (AVIC) Enablement") moved the GA log allocation from iommu_init_pci() to enable_iommus_vapic(), which is called on every resume. iommu_init_ga_log() assigns iommu->ga_log and iommu->ga_log_tail unconditionally. Each resume therefore replaces the boot-time pointers and leaks both old allocations. The function also uses GFP_KERNEL from a syscore resume callback, where interrupts are disabled and the non-boot CPUs are offline. Return early if both buffers are already allocated. Clear the pointers in free_ga_log() so a partial allocation failure cannot leave ga_log dangling.

Timeline

  1. ID reserved

    By Linux

  2. Published

  3. · 26 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 94% of all CVEs (13 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 c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b – < 8b95269d7a43b737c2c0e2fa77bf00cc8a3a4434
    • affected c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b – < ff85cdc2889e1c885eed218ee5bc0b59e0235b3f
    • affected c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b – < 94458b80d3b203c1c9e2c98aa7319b7713e006c0
    • affected c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b – < b6be275d19cee01f8f1f08a2ff18337103d05d40
    • affected c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b – < 00a7dd64888d6dd72110b40e2824a088cf7b7386
  • Linux · Linux

    • affected 6.0
    • unaffected < 6.0
    • unaffected 6.6.160 – ≤ 6.6.*
    • unaffected 6.12.114 – ≤ 6.12.*
    • unaffected 6.18.53 – ≤ 6.18.*
    • unaffected 7.2.7 – ≤ 7.2.*
    • unaffected 7.3 – ≤ *

References

References5

Sources

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

Badge for a README or a ticket

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

Record last updated .