CVE-2026-80818

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-71253 (ENISA EUVD) · GHSA-q92c-jh6h-6xrq (GitHub Security Advisories)Source: ENISA EUVD

—
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No CVSS published and no exploitation signals yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS v2: —Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

iommu/tegra241-cmdqv: Fix CMD_SYNC use-after-free on teardown

arm_smmu_impl_remove() is registered as a devres action in arm_smmu_impl_probe(), before arm_smmu_init_queues() allocates smmu->cmdq.q.base. On a devres unwind, whether a failed probe or an unbind, the queue is freed first and arm_smmu_impl_remove() then runs tegra241_cmdqv_remove_vintf(), whose VINTF deinit issues a CMD_SYNC on the freed memory.

Observed during testing with a QEMU hack that makes the VCMDQ fail to enable, so the impl reset fails and probe aborts into the devres unwind:

platform NVDA200C:00: tegra241_cmdqv: VINTF0: VCMDQ0/LVCMDQ0: failed to enable, STATUS=0x00000000 platform NVDA200C:00: tegra241_cmdqv: VINTF0: VCMDQ0/LVCMDQ0: GERRORN=0x0, GERROR=0x4, CONS=0x0 platform NVDA200C:00: tegra241_cmdqv: VINTF0: VCMDQ0/LVCMDQ0: uncleared error detected, resetting arm-smmu-v3 arm-smmu-v3.0.auto: failed to reset impl arm-smmu-v3 arm-smmu-v3.0.auto: probe with driver arm-smmu-v3 failed with error -110 Unable to handle kernel paging request at virtual address ffff8000891e0098 ... Internal error: Oops: 0000000096000047 [#1] SMP ... Call trace: arm_smmu_cmdq_issue_cmdlist+0x320/0x6fc (P) tegra241_vcmdq_hw_deinit+0x98/0x168 tegra241_vintf_hw_deinit+0x5c/0x1b0 tegra241_cmdqv_remove_vintf+0x34/0xec tegra241_cmdqv_remove+0x40/0x9c arm_smmu_impl_remove+0x20/0x30 devm_action_release+0x14/0x20 devres_release_all+0xa8/0x110 device_unbind_cleanup+0x18/0x84 really_probe+0x1f0/0x29c

Drop the VINTF deinit from tegra241_cmdqv_remove_vintf() so the unwind no longer touches the freed queue. Quiesce the VINTFs earlier instead. Add a device_disable() impl op and run it from arm_smmu_disable_action() while the CMDQ is still up. That handles a live unbind. A failed reset is already handled because tegra241_vintf_hw_init() deinits the VINTF on its own error path. tegra241_cmdqv_remove_vintf() is also used by the iommufd viommu destroy path, so quiesce there too.

CVSS v3
—
EchelonGraph score
Not yet assessedNo source has published severity data for this CVE yet — no CVSS score from NVD or a CNA, no GitHub advisory, and it is not in CISA KEV. This is not a rating of zero; we cannot assess it yet.
EG Score
—
EG Risk
—
EPSS PROB
0.2%
EPSS %ILE
10th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

EG Severity
Not assessed: no CVSS publishedA missing CVSS is not a severity of zero.
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
No SSVC decision: EchelonGraph has not assessed this CVECISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the BOD 26-04 block below.

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 4, 2026

Last Modified

October 19, 2026

References (4)

Vendor Advisories for CVE-2026-80818(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.1~rc7-1~exp1 (170 versions)
  • every version up to 7.1.12-1: fixed in 7.1.12-1
—

Data Freshness Timeline

(refreshed 8× in last 7d / 44× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 73 are merged into the row they repeat.

  1. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-25 13:59 UTCEG score recompute
  4. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-19 09:25 UTCNVD update
  11. 2026-10-19 09:23 UTCEG score recompute
  12. 2026-10-19 09:23 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  13. 2026-10-19 08:58 UTCMITRE cvelistV5
  14. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  15. 2026-10-18 03:09 UTCEG score recompute
  16. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  17. 2026-10-16 16:44 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  20. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  21. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  22. 2026-10-12 14:57 UTCEG score recompute
  23. 2026-10-11 19:21 UTCEG score recompute
  24. 2026-10-11 16:37 UTCEG score recompute
  25. 2026-10-11 13:55 UTCEG score recompute
Show 46 more
  1. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  2. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  3. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  4. 2026-10-09 01:12 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  5. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  8. 2026-10-05 20:28 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  9. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  11. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  12. 2026-10-03 00:22 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  13. 2026-10-02 17:57 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  14. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  15. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  16. 2026-09-30 03:35 UTCEG score recompute
  17. 2026-09-30 03:35 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  18. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  19. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  20. 2026-09-27 07:41 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  21. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  22. 2026-09-26 00:28 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  23. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  24. 2026-09-24 11:47 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  25. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  26. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  27. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  28. 2026-09-21 15:53 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  29. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  30. 2026-09-18 20:00 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  31. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  32. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  33. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-16 00:05 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  35. 2026-09-15 03:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-09-13 04:10 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  37. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  38. 2026-09-10 08:15 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  39. 2026-09-08 22:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  40. 2026-09-07 12:21 UTCEG score recompute
  41. 2026-09-07 12:21 UTCGHSA enrichmentGHSA-q92c-jh6h-6xrq
  42. 2026-09-06 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  43. 2026-09-05 15:31 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  44. 2026-09-04 16:22 UTCNVD update
  45. 2026-09-04 15:29 UTCEG score recompute
  46. 2026-09-04 15:29 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-80818?
CVE-2026-80818 is a vulnerability whose severity is not yet rated; its CVE record was published on September 4, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Fix CMD_SYNC use-after-free on teardown armsmmuimpl_remove() is registered as a devres action in armsmmuimplprobe(), before armsmmuinitqueues() allocates smmu->cmdq.q.base. On a devres unwind, whether a failed…
When was the CVE record for CVE-2026-80818 published?
The CVE record for CVE-2026-80818 was published on September 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 19, 2026; the record at its source may have been updated since.
Is CVE-2026-80818 actively exploited?
CVE-2026-80818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (10th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-80818?
A fix for CVE-2026-80818 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-80818 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-80818

Explore →

Is Your Infrastructure Affected by CVE-2026-80818?

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

Book a Demo →Browse All CVEs