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

> A memory leak in the Linux kernel AMD IOMMU driver during system resume can lead to resource exhaustion and denial of service.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Sep 2026
- **Updated:** 21 Oct 2026
- **Also known as:** AZL-104304, BELL-CVE-2026-98003, DEBIAN-CVE-2026-98003, GHSA-mvmg-3rw6-rj84, UBUNTU-CVE-2026-98003

## What is CVE-2026-98003?

CVE-2026-98003 is a memory corruption vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

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

## Which versions are affected by CVE-2026-98003?


## How do I fix CVE-2026-98003?

Apply the vendor's patch.

## Is CVE-2026-98003 being exploited?

There is no known exploitation of CVE-2026-98003 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-98003 and fix it if it is affected.

What it is: CVE-2026-98003 is a memory corruption vulnerability in Linux, published on 25 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-98003 in the wild and no public exploit code.

Affected product: Linux. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-98003/ (Markdown: https://insights.sbomify.com/CVE-2026-98003/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-98003
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-98003
- OSV: https://osv.dev/vulnerability/CVE-2026-98003

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-98003/
Summaries are generated and may contain mistakes; the official description above is the record.