CVE-2026-90429

HIGHPre-NVD 7.87.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source

Also known asEUVD-2026-82090 (ENISA EUVD) · GHSA-fc4x-65xv-jwjh (GitHub Security Advisories)Source: ENISA EUVD

7.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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

iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init

A user VINTF is torn down by tegra241_cmdqv_deinit_vintf(), which runs from the destroy callback and from the init-failure unwind in the alloc handler. It clears the cmdqv->vintfs[] slot and lets the iommufd core free it, but nothing serializes that against the error interrupt: tegra241_cmdqv_isr() reads cmdqv->vintfs[idx] and dereferences the vintf. A concurrent error can make the ISR read a slot mid-clear (a NULL deref) or use a vintf which is about to be freed (a use-after-free).

deinit_vintf() also returns idx to the IDA before clearing the slot, so a concurrent create that reuses idx can publish its new vintf into the slot, only for this teardown to erase it again with the stale NULL store.

On the other end, tegra241_cmdqv_init_vintf() publishes a new vintf with a plain store to the cmdqv->vintfs[] slot, and the ISR dereferences fields of a published vintf such as vintf->base. A plain store gives no ordering on a weakly-ordered CPU, and a stale VINTF_ERR_MAP bit on a reused idx can make the ISR pick a vintf the moment it is published, before its fields are set or tegra241_vintf_hw_init() runs.

The cmdqv->vintfs[0] slot stays NULL until tegra241_cmdqv_init_structures() first creates VINTF0, so the slot 0 read needs the same NULL check.

Publish every slot with an smp_store_release(), and read each slot in the ISR with an smp_load_acquire() under a NULL check, so the ISR always sees a fully built vintf or NULL. Also make deinit_vintf() clear the slot, and synchronize_irq() prior to returning idx to the IDA, so no vintf is freed under a running handler and no reused idx is clobbered.

CVSS v3
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
35
EG Risk 35/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

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

The EG score (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-17). 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
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA 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, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (no CISA value, KEV listing or exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

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.

The score's inputs: 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 17, 2026

Last Modified

October 19, 2026

Advisory Details (3)

Auto-updated Sep 18, 2026
Patch available.
Web page

iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/f3ef4abc271a1d3d7b6715879e149c286dc8aae7
Web page

iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bcb82407633c3008362ad927699d985ee4981557
Web page

iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/a491be376abd1c80a314cdd658632c85cd660b73

Vendor Advisories for CVE-2026-90429(2)

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

Patch Availability(5)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntulinux-tools-oem-7.0 (7.0.0-1017.17) @ resolute2026-11-11ubuntu
ubuntulinux-tools-realtime-hwe-26.04-edge (7.0.0-43.43.1) @ resolute2026-11-11ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-42.42) @ resolute2026-11-11ubuntu
ubuntulinux-tools-azure-lts-26.04 (7.0.0-1020.21) @ resolute2026-11-11ubuntu
linuxKernel @ 6.18.52 (fixes >=6.17.0)—osv

These rows come from Ubuntu and OSV. Multiple rows for the same upstream release have been deduplicated.

Affected Packages

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

Additional Vendor Advisories

(4)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 161 rows on record for this CVE.

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. None are among the latest 100 rows. The 61 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 19:56 UTCOSV refresh
  2. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-11-18 04:26 UTCEchelonGraph re-scored
  7. 2026-11-18 04:26 UTCVendor advisory
  8. 2026-11-18 04:26 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-11-15 17:03 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-11-11 01:36 UTCEchelonGraph re-scored
  15. 2026-11-11 01:36 UTCVendor advisory
  16. 2026-11-11 01:36 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-11-03 21:54 UTCEchelonGraph re-scored
  25. 2026-11-03 21:54 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
Show 75 more
  1. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-27 18:09 UTCEchelonGraph re-scored
  9. 2026-10-27 18:09 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-25 13:52 UTCEchelonGraph re-scored
  14. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-19 09:33 UTCEchelonGraph re-scored
  21. 2026-10-19 09:33 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-19 09:10 UTCEchelonGraph re-scored
  23. 2026-10-19 09:10 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-18 03:01 UTCEchelonGraph re-scored
  26. 2026-10-17 18:34 UTCEchelonGraph re-scored
  27. 2026-10-17 18:34 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  29. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  30. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  31. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  32. 2026-10-13 04:46 UTCEchelonGraph re-scored
  33. 2026-10-13 04:46 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  34. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-10-12 14:46 UTCEchelonGraph re-scored
  36. 2026-10-11 20:52 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  37. 2026-10-11 19:14 UTCEchelonGraph re-scored
  38. 2026-10-11 16:30 UTCEchelonGraph re-scored
  39. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-10-11 13:45 UTCEchelonGraph re-scored
  41. 2026-10-11 08:51 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-10-10 20:16 UTCEchelonGraph re-scored
  43. 2026-10-10 20:16 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  44. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-10-10 08:18 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-10-09 20:21 UTCEchelonGraph re-scored
  47. 2026-10-09 20:21 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  49. 2026-10-09 08:24 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-10-08 20:27 UTCEchelonGraph re-scored
  51. 2026-10-08 20:27 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  53. 2026-10-08 06:55 UTCEchelonGraph re-scored
  54. 2026-10-08 06:55 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  56. 2026-10-07 18:58 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-10-07 07:01 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-10-06 19:04 UTCEchelonGraph re-scored
  59. 2026-10-06 19:04 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  61. 2026-10-06 07:03 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-10-05 18:54 UTCEchelonGraph re-scored
  63. 2026-10-05 18:54 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  65. 2026-10-05 06:58 UTCEchelonGraph re-scored
  66. 2026-10-05 06:58 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  68. 2026-10-04 19:01 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-10-04 06:46 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-10-03 18:49 UTCEchelonGraph re-scored
  71. 2026-10-03 18:49 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-10-03 06:18 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-10-02 18:20 UTCEchelonGraph re-scored
  74. 2026-10-02 18:20 UTCGHSA enrichmentGHSA-fc4x-65xv-jwjh · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-10-02 06:23 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-90429?
CVE-2026-90429 is a high-severity vulnerability; its CVE record was published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Synchronize the error ISR against VINTF (de)init A user VINTF is torn down by tegra241_cmdqv_deinit_vintf(), which runs from the destroy callback and from the init-failure unwind in the alloc handler. It…
When was the CVE record for CVE-2026-90429 published?
The CVE record for CVE-2026-90429 was published on September 17, 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-90429 actively exploited?
CVE-2026-90429 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90429?
CVE-2026-90429 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-90429?
A fix for CVE-2026-90429 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90429 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-90429

Explore →

Is Your Infrastructure Affected by CVE-2026-90429?

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