CVE-2026-98002

HIGHPre-NVD 7.87.8—
EchelonGraph scoreHIGH confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-09-25. A secondary CVSS source baseline 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.8EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 7.8Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

In the Linux kernel, the following vulnerability has been resolved:

iommu/amd: Fix ineffective error check in nested domain allocation

amd_iommu_pdom_id_alloc() returns an int: a domain ID on success, or the negative errno from ida_alloc_range() when the ID space is exhausted or memory is short. amd_iommu_alloc_domain_nested() stores that return value in gdom_info->hdom_id, which is a u32, and only then tests it:

gdom_info->hdom_id = amd_iommu_pdom_id_alloc(); if (gdom_info->hdom_id <= 0) {

The assignment discards the sign, so -ENOSPC becomes 0xffffffe4 and the test never fires. The nested domain is then set up with a host domain ID that was never allocated, instead of the allocation failing with -ENOSPC.

Keep the value in an int, test it there, and store it only once it is known to be valid, which is what the other amd_iommu_pdom_id_alloc() callers already do.

CVSS v3
7.8
EG Score
7.8HIGHhigh confidence
EG Risk
40
EG Risk 40/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
CISA SSVC: Track at low or medium mission impact; Track or Attend at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
0.1%
EPSS %ILE
1st
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track or Attend at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation none (no KEV listing, exploit record or EPSS ≥ 50%) · Automatable unknown (not published for this CVE) · Technical impact partial (CVSS below 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

September 25, 2026

Last Modified

September 25, 2026

Advisory Details (2)

Auto-updated Sep 25, 2026
No patch confirmed yet.
generic

iommu/amd: Fix ineffective error check in nested domain allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/fa5c0827f0b7bac6d0a188f10118151769ae68fd
generic

iommu/amd: Fix ineffective error check in nested domain allocation - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/80c231f5577229d1e90a1e312b3095f9502f8625

Vendor Advisories for CVE-2026-98002(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (179 versions)
  • every version up to 7.2.7-1: fixed in 7.2.7-1
—

Data Freshness Timeline

(refreshed 21× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:23 UTCEPSS rescore
  2. 2026-10-04 23:20 UTCGHSA enrichment
  3. 2026-10-04 10:11 UTCGHSA enrichment
  4. 2026-10-03 21:01 UTCEG score recompute
  5. 2026-10-03 21:01 UTCGHSA enrichment
  6. 2026-10-03 14:26 UTCEPSS rescore
  7. 2026-10-03 07:51 UTCGHSA enrichment
  8. 2026-10-02 18:39 UTCGHSA enrichment
  9. 2026-10-02 05:29 UTCEG score recompute
  10. 2026-10-02 05:29 UTCGHSA enrichment
  11. 2026-10-01 19:51 UTCEPSS rescore
  12. 2026-10-01 16:16 UTCGHSA enrichment
  13. 2026-10-01 03:07 UTCEG score recompute
  14. 2026-10-01 03:07 UTCGHSA enrichment
  15. 2026-09-30 15:04 UTCEPSS rescore
  16. 2026-09-30 13:57 UTCGHSA enrichment
  17. 2026-09-30 00:48 UTCEG score recompute
  18. 2026-09-30 00:48 UTCGHSA enrichment
  19. 2026-09-29 11:39 UTCGHSA enrichment
  20. 2026-09-28 22:26 UTCEG score recompute
  21. 2026-09-28 22:26 UTCGHSA enrichment
  22. 2026-09-28 09:16 UTCGHSA enrichment
  23. 2026-09-27 20:07 UTCGHSA enrichment
  24. 2026-09-27 06:58 UTCGHSA enrichment
  25. 2026-09-26 17:48 UTCEG score recompute
Show 12 more
  1. 2026-09-26 17:48 UTCGHSA enrichment
  2. 2026-09-26 15:59 UTCEPSS rescore
  3. 2026-09-26 04:38 UTCEG score recompute
  4. 2026-09-26 04:37 UTCGHSA enrichment
  5. 2026-09-25 15:24 UTCEG score recompute
  6. 2026-09-25 15:24 UTCGHSA enrichment
  7. 2026-09-25 14:52 UTCEG score recompute▲ 7.80
  8. 2026-09-25 14:52 UTCGHSA enrichment
  9. 2026-09-25 14:49 UTCMITRE cvelistV5CVSS v3 → 7.8 · severity → HIGH
  10. 2026-09-25 11:30 UTCNVD update
  11. 2026-09-25 10:30 UTCEG score recompute
  12. 2026-09-25 10:27 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-98002?
CVE-2026-98002 is a high vulnerability published on September 25, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/amd: Fix ineffective error check in nested domain allocation amdiommupdomidalloc() returns an int: a domain ID on success, or the negative errno from idaallocrange() when the ID space is exhausted or memory is short.…
When was CVE-2026-98002 disclosed?
CVE-2026-98002 was first published on September 25, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-98002 actively exploited?
CVE-2026-98002 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-98002?
CVE-2026-98002 has a CVSS base score of 7.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-98002?
No fix for CVE-2026-98002 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-98002 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-98002

Explore →

Is Your Infrastructure Affected by CVE-2026-98002?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.