CVE-2026-46075

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

Score 7.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-27. NVD baseline CVSS 7.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

A fix is available — apply it.

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

crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path

Unregister the hwrng to prevent new ->read() calls and flush the Atmel I2C workqueue before teardown to prevent a potential UAF if a queued callback runs while the device is being removed.

Drop the early return to ensure sysfs entries are removed and ->hwrng.priv is freed, preventing a memory leak.

CVSS v3
7.8
EG Score
7.8(medium)
EPSS
2.9%
KEV
Not listed

Published

May 27, 2026

Last Modified

June 24, 2026

Advisory Details (6)

Auto-updated Jun 24, 2026
No patch confirmed yet.
generic

crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/c5a45d14234bf26e28a89e3a5dcc08336595cf11
generic

crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/bab1adf3b87e4bfac92c4f5963c63db434d561c1
generic

crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/775c00d87c385b758da9504cf053acea00e2ed40
generic

crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/6dbeb0f788582e1ab5dfc3f41994eac0ec88c2b5
generic

crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/31901371ccd16b42d2f167b1018ba9ae8bd5a6c7
generic

crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path - kernel/git/stable/linux.git - Linux kernel stable tree

https://git.kernel.org/stable/c/1193c12126d39bf986a5a9214827b73707b193ab

Vendor Advisories for CVE-2026-46075(2)

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-11ubuntu
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-07-11ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-07-11ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-07-11ubuntu

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.

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 10× in last 7d / 77× 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.

Showing the most recent 100 of 118 total refreshes for this CVE.

  1. 2026-07-15 16:57 UTCEPSS rescore
  2. 2026-07-15 02:00 UTCEPSS rescore
  3. 2026-07-13 22:30 UTCEPSS rescore
  4. 2026-07-13 06:13 UTCEPSS rescore
  5. 2026-07-12 05:46 UTCEPSS rescore
  6. 2026-07-11 23:35 UTCEG score recompute
  7. 2026-07-11 23:35 UTCVendor advisory
  8. 2026-07-11 23:34 UTCGHSA enrichment
  9. 2026-07-11 08:27 UTCEPSS rescore
  10. 2026-07-09 19:10 UTCEPSS rescore
  11. 2026-07-08 23:50 UTCEG score recompute
  12. 2026-07-08 23:50 UTCVendor advisory
  13. 2026-07-08 23:50 UTCGHSA enrichment
  14. 2026-07-08 15:16 UTCEPSS rescore
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-06 16:27 UTCEPSS rescore
  17. 2026-07-06 02:23 UTCEPSS rescore
  18. 2026-07-05 02:30 UTCEPSS rescore
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-01 15:07 UTCEPSS rescore
  21. 2026-07-01 10:12 UTCEG score recompute
  22. 2026-07-01 10:12 UTCVendor advisory
  23. 2026-07-01 10:12 UTCGHSA enrichment
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 03:20 UTCEG score recompute
Show 75 more
  1. 2026-06-30 03:20 UTCVendor advisory
  2. 2026-06-30 03:20 UTCGHSA enrichment
  3. 2026-06-29 14:19 UTCEG score recompute
  4. 2026-06-29 14:19 UTCVendor advisory
  5. 2026-06-29 14:19 UTCGHSA enrichment
  6. 2026-06-29 14:06 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 20:51 UTCEG score recompute
  9. 2026-06-28 20:51 UTCVendor advisory
  10. 2026-06-28 20:51 UTCGHSA enrichment
  11. 2026-06-28 14:07 UTCEPSS rescore
  12. 2026-06-28 06:43 UTCEG score recompute
  13. 2026-06-28 06:43 UTCVendor advisory
  14. 2026-06-28 06:43 UTCGHSA enrichment
  15. 2026-06-28 04:56 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-27 18:29 UTCEG score recompute
  18. 2026-06-27 18:29 UTCVendor advisory
  19. 2026-06-27 18:29 UTCGHSA enrichment
  20. 2026-06-27 05:49 UTCEG score recompute
  21. 2026-06-27 05:49 UTCVendor advisory
  22. 2026-06-27 05:49 UTCGHSA enrichment
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 17:06 UTCEG score recompute
  25. 2026-06-26 17:06 UTCVendor advisory
  26. 2026-06-26 17:06 UTCGHSA enrichment
  27. 2026-06-26 02:27 UTCEG score recompute
  28. 2026-06-26 02:27 UTCVendor advisory
  29. 2026-06-26 02:27 UTCGHSA enrichment
  30. 2026-06-25 13:49 UTCEPSS rescore
  31. 2026-06-25 12:27 UTCEG score recompute
  32. 2026-06-25 12:27 UTCVendor advisory
  33. 2026-06-25 12:27 UTCGHSA enrichment
  34. 2026-06-25 01:02 UTCEG score recompute▲ 7.80
  35. 2026-06-25 01:02 UTCVendor advisory
  36. 2026-06-25 01:02 UTCGHSA enrichment
  37. 2026-06-24 18:02 UTCNVD updateCVSS v3 → 7.8 · severity → HIGH
  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-21 14:56 UTCEPSS rescore
  44. 2026-06-21 14:56 UTCEPSS rescore
  45. 2026-06-21 01:59 UTCEPSS rescore
  46. 2026-06-21 01:59 UTCEPSS rescore
  47. 2026-06-19 19:26 UTCEPSS rescore
  48. 2026-06-19 19:26 UTCEPSS rescore
  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:52 UTCEPSS rescore
  53. 2026-06-15 22:18 UTCVendor advisory
  54. 2026-06-15 22:18 UTCGHSA enrichment
  55. 2026-06-15 17:49 UTCEPSS rescore
  56. 2026-06-14 23:28 UTCMITRE cvelistV5
  57. 2026-06-13 23:00 UTCEPSS rescore
  58. 2026-06-12 23:12 UTCEPSS rescore
  59. 2026-06-12 23:12 UTCEPSS rescore
  60. 2026-06-12 20:53 UTCVendor advisory
  61. 2026-06-12 20:53 UTCGHSA enrichment
  62. 2026-06-11 14:00 UTCEPSS rescore
  63. 2026-06-10 22:18 UTCEPSS rescore
  64. 2026-06-10 13:22 UTCEPSS rescore
  65. 2026-06-10 13:22 UTCEPSS rescore
  66. 2026-06-09 22:03 UTCGHSA enrichment
  67. 2026-06-08 14:17 UTCEPSS rescore
  68. 2026-06-08 14:17 UTCEPSS rescore
  69. 2026-06-07 15:25 UTCEPSS rescore
  70. 2026-06-07 15:25 UTCEPSS rescore
  71. 2026-06-06 23:13 UTCGHSA enrichment
  72. 2026-06-06 13:47 UTCEPSS rescore
  73. 2026-06-06 13:47 UTCEPSS rescore
  74. 2026-06-05 22:47 UTCEPSS rescore
  75. 2026-06-05 06:10 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-46075?
CVE-2026-46075 is a high vulnerability published on May 27, 2026. In the Linux kernel, the following vulnerability has been resolved: crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path Unregister the hwrng to prevent new ->read() calls and flush the Atmel I2C workqueue before teardown to prevent a potential UAF if a queued callback runs…
When was CVE-2026-46075 disclosed?
CVE-2026-46075 was first published in the National Vulnerability Database on May 27, 2026, with the most recent update on June 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-46075 actively exploited?
CVE-2026-46075 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 2.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-46075?
CVE-2026-46075 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-46075?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-46075, 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-46075

Explore →

Is Your Infrastructure Affected by CVE-2026-46075?

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

Start Free Scan →Browse All CVEs