CVE-2026-46285

CVSS 0.0Trending — 3 sources updated this week
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 0%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

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

mtd: docg3: fix use-after-free in docg3_release()

In docg3_release(), the docg3 pointer is obtained from cascade->floors[0]->priv before the loop that calls doc_release_device() on each floor. doc_release_device() frees the docg3 struct via kfree(docg3) at line 1881. After the loop, docg3->cascade->bch dereferences the already-freed pointer.

Fix this by accessing cascade->bch directly, which is equivalent since docg3->cascade points back to the same cascade struct, and is already available as a local variable. This also removes the now-unused docg3 local variable.

CVSS v3
—
EG Score
0.0(none)
EPSS
7.4%
KEV
Not listed

Published

June 8, 2026

Last Modified

June 14, 2026

References (8)

Vendor Advisories for CVE-2026-46285(2)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-02ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-02ubuntu

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.

Additional Vendor Advisories

(2)

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 10× in last 7d / 54× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 02:23 UTCEPSS rescore
  3. 2026-07-05 17:34 UTCVendor advisory
  4. 2026-07-05 17:34 UTCGHSA enrichment
  5. 2026-07-05 02:30 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-02 12:18 UTCVendor advisory
  8. 2026-07-02 12:18 UTCGHSA enrichment
  9. 2026-07-01 15:07 UTCEPSS rescore
  10. 2026-06-30 23:22 UTCEPSS rescore
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 13:17 UTCVendor advisory
  14. 2026-06-29 13:17 UTCGHSA enrichment
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-27 03:08 UTCEPSS rescore
  19. 2026-06-26 14:50 UTCVendor advisory
  20. 2026-06-26 14:50 UTCGHSA enrichment
  21. 2026-06-25 13:49 UTCEPSS rescore
  22. 2026-06-24 14:05 UTCEPSS rescore
  23. 2026-06-23 21:33 UTCEPSS rescore
  24. 2026-06-23 21:33 UTCEPSS rescore
  25. 2026-06-23 16:01 UTCVendor advisory
Show 29 more
  1. 2026-06-23 16:01 UTCGHSA enrichment
  2. 2026-06-22 14:25 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-21 14:56 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 01:59 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-20 10:53 UTCVendor advisory
  9. 2026-06-20 10:53 UTCGHSA enrichment
  10. 2026-06-19 19:26 UTCEPSS rescore
  11. 2026-06-19 19:26 UTCEPSS rescore
  12. 2026-06-18 17:52 UTCEPSS rescore
  13. 2026-06-18 17:52 UTCEPSS rescore
  14. 2026-06-17 17:53 UTCEPSS rescore
  15. 2026-06-17 12:25 UTCGHSA enrichment
  16. 2026-06-16 17:52 UTCEPSS rescore
  17. 2026-06-15 17:49 UTCEPSS rescore
  18. 2026-06-14 23:33 UTCMITRE cvelistV5
  19. 2026-06-14 13:51 UTCGHSA enrichment
  20. 2026-06-13 23:00 UTCEPSS rescore
  21. 2026-06-12 23:12 UTCEPSS rescore
  22. 2026-06-12 23:12 UTCEPSS rescore
  23. 2026-06-11 15:25 UTCEG score recompute
  24. 2026-06-11 15:25 UTCGHSA enrichment
  25. 2026-06-11 14:00 UTCEPSS rescore
  26. 2026-06-10 22:18 UTCEPSS rescore
  27. 2026-06-10 13:22 UTCEPSS rescore
  28. 2026-06-10 13:22 UTCEPSS rescore
  29. 2026-06-08 16:59 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-46285?
CVE-2026-46285 is a publicly disclosed vulnerability published on June 8, 2026. In the Linux kernel, the following vulnerability has been resolved: mtd: docg3: fix use-after-free in docg3_release() In docg3_release(), the docg3 pointer is obtained from cascade->floors[0]->priv before the loop that calls docreleasedevice() on each floor. docreleasedevice() frees the docg3…
When was CVE-2026-46285 disclosed?
CVE-2026-46285 was first published in the National Vulnerability Database on June 8, 2026, with the most recent update on June 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46285 actively exploited?
CVE-2026-46285 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2026-46285?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46285, 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-46285

Explore →

Is Your Infrastructure Affected by CVE-2026-46285?

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

Start Free Scan →Browse All CVEs