CVE-2026-90424

UNRATEDCVSS · not yet scored

Also known asEUVD-2026-82085 (ENISA EUVD) · GHSA-f39c-j3gp-39r5 (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 VINTF0 leak on the init-failure path

tegra241_cmdqv_init_structures() allocates VINTF0 with kzalloc_obj(), inits it, and preallocates its logical VCMDQs. Two of its error paths leak.

When tegra241_cmdqv_init_vintf() fails it returns before VINTF0 reaches the cmdqv->vintfs[] array, so the devres unwind on probe failure cannot reach it; free it directly there.

A later VCMDQ preallocation failure instead leaves VINTF0 published, and so this time the unwind does reach tegra241_cmdqv_remove_vintf(), which then frees it from vintf->hyp_own. But tegra241_vintf_hw_init() sets that flag only afterward, from a HW read-back, so the still-uninited VINTF0 reads as guest-owned and leaks, with mutex_destroy() and ida_destroy() run on fields it never set up.

Decide ownership from vintf->idx instead, the index assigned when its id is allocated: idx 0 is the kernel-owned VINTF0, while idx >= 1 marks a guest VINTF. So the in-kernel free decision in tegra241_cmdqv_remove_vintf() and tegra241_vintf_free_lvcmdq() now keys on idx too, and hyp_own stays a pure HW-readback state.

CVSS
—
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
6th
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-11-18). 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, and whom BOD 26-04 binds: 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.

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 21, 2026

Vendor Advisories for CVE-2026-90424(2)

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

Patch Availability(6)

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

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

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 6.12.96-1 (38 versions)
  • every version up to 6.12.115-2: fixed in 6.12.115-2
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
linux6.12.100-1 ... 7.2~rc7-1~exp1 (182 versions)
  • every version up to 7.2.6-1: fixed in 7.2.6-1
—

Additional Vendor Advisories

(5)

Data Freshness Timeline

(refreshed 8× in last 7d / 31× 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 → 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.

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. 1 repeat row among the latest 93 is merged into the row it repeats.

  1. 2026-11-21 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  2. 2026-11-20 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  3. 2026-11-19 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-11-18 18:27 UTCEchelonGraph re-scored
  5. 2026-11-18 18:27 UTCVendor advisory
  6. 2026-11-18 18:27 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  7. 2026-11-18 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-11-17 16:36 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-11-16 16:53 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-11-15 17:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-11-14 16:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-11-13 16:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  20. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  21. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  22. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  23. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  24. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  25. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 11th percentile
Show 67 more
  1. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  2. 2026-10-29 08:25 UTCOSV refresh
  3. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 11th percentile
  4. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  5. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  6. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  7. 2026-10-25 13:52 UTCEchelonGraph re-scored
  8. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  9. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  10. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  11. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  12. 2026-10-21 14:00 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  13. 2026-10-21 13:47 UTCNVD update
  14. 2026-10-21 13:09 UTCMITRE cvelistV5
  15. 2026-10-21 13:09 UTCEchelonGraph re-scored
  16. 2026-10-21 13:09 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  17. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  19. 2026-10-19 10:12 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  20. 2026-10-19 09:26 UTCNVD update
  21. 2026-10-19 09:15 UTCEchelonGraph re-scored
  22. 2026-10-19 09:15 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  23. 2026-10-19 09:08 UTCMITRE cvelistV5
  24. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  25. 2026-10-18 03:01 UTCEchelonGraph re-scored
  26. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  27. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  28. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  29. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  30. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  31. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  32. 2026-10-12 14:46 UTCEchelonGraph re-scored
  33. 2026-10-11 19:14 UTCEchelonGraph re-scored
  34. 2026-10-11 16:30 UTCEchelonGraph re-scored
  35. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  36. 2026-10-11 13:45 UTCEchelonGraph re-scored
  37. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  38. 2026-10-10 14:27 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  39. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  40. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  41. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  42. 2026-10-07 18:05 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  43. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  44. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  45. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  46. 2026-10-04 20:29 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  47. 2026-10-02 00:08 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  48. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  49. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  50. 2026-09-29 03:10 UTCEchelonGraph re-scored
  51. 2026-09-29 03:10 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  52. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  53. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  54. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  55. 2026-09-26 06:49 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  56. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  57. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  58. 2026-09-23 10:25 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  59. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  60. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  61. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  62. 2026-09-20 14:04 UTCEchelonGraph re-scored
  63. 2026-09-20 14:04 UTCGHSA enrichmentGHSA-f39c-j3gp-39r5
  64. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  65. 2026-09-17 17:24 UTCNVD update
  66. 2026-09-17 16:24 UTCEchelonGraph re-scored
  67. 2026-09-17 16:19 UTCMITRE cvelistV5first tracked

Frequently asked(4)

What is CVE-2026-90424?
CVE-2026-90424 is a vulnerability whose severity is not yet rated; its CVE record was published on September 17, 2026. In the Linux kernel, the following vulnerability has been resolved: iommu/tegra241-cmdqv: Fix VINTF0 leak on the init-failure path tegra241_cmdqv_init_structures() allocates VINTF0 with kzalloc_obj(), inits it, and preallocates its logical VCMDQs. Two of its error paths leak. When…
When was the CVE record for CVE-2026-90424 published?
The CVE record for CVE-2026-90424 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 21, 2026; the record at its source may have been updated since.
Is CVE-2026-90424 actively exploited?
CVE-2026-90424 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
How do I remediate CVE-2026-90424?
A fix for CVE-2026-90424 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90424 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-90424

Explore →

Is Your Infrastructure Affected by CVE-2026-90424?

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