CVE-2026-52904

MEDIUMNVD 5.55.5—
EchelonGraph scoreMEDIUM confidence

Score 5.5 from GitHub Security Advisory published 2026-06-09. NVD baseline CVSS 5.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.5Exploit: None knownExposed: 0

A fix is available — apply it.

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

drm/nouveau: fix nvkm_device leak on aperture removal failure

When aperture_remove_conflicting_pci_devices() fails during probe, the error path returns directly without unwinding the nvkm_device that was just allocated by nvkm_device_pci_new(). This leaks both the device wrapper and the pci_enable_device() reference taken inside it.

Jump to the existing fail_nvkm label so nvkm_device_del() runs and balances both. The leak was introduced when the intermediate nvkm_device_del() between detection and aperture removal was dropped in favor of creating the pci device once.

CVSS v3
5.5
EG Score
5.5(medium)
EG Risk
29(Track)
EG Risk 29/100SSVC: Track

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
Severity55% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
2%
KEV
Not listed

Published

June 9, 2026

Last Modified

July 23, 2026

Advisory Details (4)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

drm/nouveau: fix nvkm_device leak on aperture removal failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/843c0247cf21364e33bb5a8ffc9af57107d04d05
generic

drm/nouveau: fix nvkm_device leak on aperture removal failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6597ff1d8de3f583be169587efeafd8af134e138
generic

drm/nouveau: fix nvkm_device leak on aperture removal failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/5edd564ccb002ffc830e7818c1c4a992db774678
generic

drm/nouveau: fix nvkm_device leak on aperture removal failure - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/4404d7d2dda4f3cc84a8fb6ac5417a2afc3b22d6

Vendor Advisories for CVE-2026-52904(1)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-07-15ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-15ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-15ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-15ubuntu

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 11× in last 7d / 59× 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-07-27 08:23 UTCEG score recompute
  2. 2026-07-27 08:23 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 06:53 UTCEG score recompute
  5. 2026-07-26 06:52 UTCGHSA enrichment
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 03:19 UTCEG score recompute
  10. 2026-07-22 14:08 UTCEPSS rescore
  11. 2026-07-21 15:25 UTCEPSS rescore
  12. 2026-07-20 17:08 UTCEPSS rescore
  13. 2026-07-19 14:31 UTCEPSS rescore
  14. 2026-07-19 14:31 UTCEPSS rescore
  15. 2026-07-19 02:29 UTCEPSS rescore
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-15 20:13 UTCVendor advisory
  18. 2026-07-15 20:13 UTCGHSA enrichment
  19. 2026-07-15 16:57 UTCEPSS rescore
  20. 2026-07-15 16:57 UTCEPSS rescore
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-15 02:00 UTCEPSS rescore
  23. 2026-07-14 02:24 UTCGHSA enrichment
  24. 2026-07-13 22:31 UTCEPSS rescore
  25. 2026-07-13 06:13 UTCEPSS rescore
Show 66 more
  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-12 05:46 UTCEPSS rescore
  3. 2026-07-11 23:25 UTCEG score recompute▲ 5.50
  4. 2026-07-11 23:25 UTCVendor advisory
  5. 2026-07-11 23:25 UTCGHSA enrichment
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-08 22:53 UTCNVD updateCVSS v3 → 5.5 · severity → MEDIUM
  11. 2026-07-08 18:36 UTCGHSA enrichment
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-07 20:14 UTCNVD update
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 16:27 UTCEPSS rescore
  19. 2026-07-06 02:23 UTCEPSS rescore
  20. 2026-07-06 02:23 UTCEPSS rescore
  21. 2026-07-05 13:47 UTCVendor advisory
  22. 2026-07-05 13:47 UTCGHSA enrichment
  23. 2026-07-05 02:30 UTCEPSS rescore
  24. 2026-07-04 06:31 UTCEPSS rescore
  25. 2026-07-02 02:18 UTCVendor advisory
  26. 2026-07-02 02:18 UTCGHSA enrichment
  27. 2026-07-01 15:07 UTCEPSS rescore
  28. 2026-06-30 23:22 UTCEPSS rescore
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-28 21:29 UTCGHSA enrichment
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-28 04:56 UTCEPSS rescore
  35. 2026-06-27 03:08 UTCEPSS rescore
  36. 2026-06-25 16:38 UTCGHSA enrichment
  37. 2026-06-25 13:49 UTCEPSS rescore
  38. 2026-06-24 14:05 UTCEPSS rescore
  39. 2026-06-23 21:33 UTCEPSS rescore
  40. 2026-06-23 21:33 UTCEPSS rescore
  41. 2026-06-22 14:25 UTCEPSS rescore
  42. 2026-06-22 14:25 UTCEPSS rescore
  43. 2026-06-22 11:45 UTCGHSA enrichment
  44. 2026-06-21 01:59 UTCEPSS rescore
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-19 19:26 UTCEPSS rescore
  47. 2026-06-19 19:26 UTCEPSS rescore
  48. 2026-06-19 04:21 UTCGHSA enrichment
  49. 2026-06-18 17:52 UTCEPSS rescore
  50. 2026-06-18 17:52 UTCEPSS rescore
  51. 2026-06-17 17:53 UTCEPSS rescore
  52. 2026-06-16 17:53 UTCEPSS rescore
  53. 2026-06-15 23:00 UTCGHSA enrichment
  54. 2026-06-15 17:49 UTCEPSS rescore
  55. 2026-06-15 17:49 UTCEPSS rescore
  56. 2026-06-14 23:33 UTCMITRE cvelistV5
  57. 2026-06-14 23:18 UTCEPSS rescore
  58. 2026-06-13 23:00 UTCEPSS rescore
  59. 2026-06-12 23:12 UTCEPSS rescore
  60. 2026-06-12 23:12 UTCEPSS rescore
  61. 2026-06-12 18:12 UTCGHSA enrichment
  62. 2026-06-11 14:00 UTCEPSS rescore
  63. 2026-06-10 22:19 UTCEPSS rescore
  64. 2026-06-09 15:17 UTCNVD update
  65. 2026-06-09 13:22 UTCEG score recompute
  66. 2026-06-09 13:22 UTCMITRE cvelistV5first tracked

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-52904?
CVE-2026-52904 is a medium vulnerability published on June 9, 2026. In the Linux kernel, the following vulnerability has been resolved: drm/nouveau: fix nvkm_device leak on aperture removal failure When apertureremoveconflictingpcidevices() fails during probe, the error path returns directly without unwinding the nvkm_device that was just allocated by…
When was CVE-2026-52904 disclosed?
CVE-2026-52904 was first published in the National Vulnerability Database on June 9, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-52904 actively exploited?
CVE-2026-52904 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 98.3% of all scored CVEs.
What is the CVSS score of CVE-2026-52904?
CVE-2026-52904 has a CVSS v3 base score of 5.5 (NVD).
How do I remediate CVE-2026-52904?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-52904, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-52904

Explore →

Is Your Infrastructure Affected by CVE-2026-52904?

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

Start Free Scan →Browse All CVEs