CVE-2026-98003: iommu/amd: Do not reallocate GA log buffers on resume
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.16% (FIRST EPSS).
- Fixed version: Linux Linux 00a7dd64888d6dd72110b40e2824a088cf7b7386, 8b95269d7a43b737c2c0e2fa77bf00cc8a3a4434, 94458b80d3b203c1c9e2c98aa7319b7713e006c0; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes.
- Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).
Low priority for now. Upgrade to Linux Linux 00a7dd64888d6dd72110b40e2824a088cf7b7386, 8b95269d7a43b737c2c0e2fa77bf00cc8a3a4434, 94458b80d3b203c1c9e2c98aa7319b7713e006c0; azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 Release Notes 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: 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.
- Published
- Sep 25, 2026
- Updated
- Oct 21, 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
- c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b and later · before 8b95269d7a43b737c2c0e2fa77bf00cc8a3a4434affected · git
- c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b and later · before ff85cdc2889e1c885eed218ee5bc0b59e0235b3faffected · git
- c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b and later · before 94458b80d3b203c1c9e2c98aa7319b7713e006c0affected · git
- c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b and later · before b6be275d19cee01f8f1f08a2ff18337103d05d40affected · git
- c5e1a1eb9279fdb28d47ca2a4493a4c53b7d6a0b and later · before 00a7dd64888d6dd72110b40e2824a088cf7b7386affected · git
- before 6.0not affected · semver
- 6.6.160 and later · up to and including 6.6.*not affected · semver
- 6.12.114 and later · up to and including 6.12.*not affected · semver
- 6.18.53 and later · up to and including 6.18.*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 | from 0 | — |
| Debian:14 | linux | before 7.2.7-1 | 7.2.7-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-98001Sep 25, 2026 · hwmon: (ltc4282) Make sure clk_init_data is fully initialized0Monitor
- ← EarlierCVE-2026-98002Sep 25, 2026 · iommu/amd: Fix ineffective error check in nested domain allocation31Monitor
- Later →CVE-2026-98004Sep 25, 2026 · iommu/riscv: Serialize command queue publishing0Monitor
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 | 00a7dd64888d6dd72110b40e2824a088cf7b7386 | Vendor (CNA) |
| Linux Linux | 8b95269d7a43b737c2c0e2fa77bf00cc8a3a4434 | Vendor (CNA) |
| Linux Linux | 94458b80d3b203c1c9e2c98aa7319b7713e006c0 | Vendor (CNA) |
| Linux Linux | b6be275d19cee01f8f1f08a2ff18337103d05d40 | Vendor (CNA) |
| Linux Linux | ff85cdc2889e1c885eed218ee5bc0b59e0235b3f | Vendor (CNA) |
| azl3 kernel 6.6.157.1-1 on Azure Linux 3.0 | Release Notes | Microsoft (MSRC) |
| debian:linux | 7.2.7-1 · Debian:14 | 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-1184 · Sep 28, 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 (4 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.