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
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.8Exploit: None knownExposed: 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)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
3%
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(20)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntulinux-virtual-hwe-26.04-edge (7.0.0-27.27) @ resolute2026-08-25ubuntu
ubuntulinux-tools-oem-7.0 (7.0.0-1008.8) @ resolute2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-7.0 (7.0.0-1014.14) @ resolute2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-24.04-edge (7.0.0-1013.13) @ resolute2026-08-25ubuntu
ubuntulinux-virtual-6.8 (6.8.0-136.136) @ noble2026-08-25ubuntu
ubuntulinux-tools-nvidia-hwe-22.04-edge (6.8.0-1059.62~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-oracle-lts-24.04 (6.8.0-1058.61) @ noble2026-08-25ubuntu
ubuntulinux-tools-aws-lts-24.04 (6.8.0-1061.64+1) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-22.04-edge (6.8.0-136.136~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-raspi-realtime-6.8 (6.8.0-2050.52) @ noble2026-08-25ubuntu
ubuntulinux-virtual-hwe-24.04-edge (7.0.0-28.28~24.04.1) @ noble2026-08-25ubuntu
ubuntulinux-tools-gcp-fips-6.8 (6.8.0-1064.72+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-oracle-edge (6.8.0-1058.61~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-azure-fde-7.0 (7.0.0-1009.9) @ resolute2026-08-25ubuntu
ubuntulinux-tools-azure-lts-24.04 (6.8.0-1063.71) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-lts-24.04 (6.8.0-1062.69) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fips-6.8 (6.8.0-1063.71+fips2) @ noble2026-08-25ubuntu
ubuntulinux-tools-azure-fde-6.8 (6.8.0-1062.69~22.04.1) @ jammy2026-08-25ubuntu
ubuntulinux-tools-aws-fips-6.8 (6.8.0-1061.64+fips1) @ noble2026-08-25ubuntu
ubuntulinux-tools-ibm-edge (6.8.0-1061.62~22.04.1) @ jammy2026-08-25ubuntu

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.

Affected Packages

(5 across 4 ecosystems)
Debian:11(2)
PackageVulnerable rangeFixed inDependents
linux5.10.103-1 ... 7.2~rc5-1~exp1 (496 versions)
linux-6.16.1.106-3~deb11u1 ... 6.1.174-1~deb11u1 (20 versions)6.1.176-1~deb11u1
Debian:12(1)
PackageVulnerable rangeFixed inDependents
linux6.1.106-1 ... 6.1.99-1 (53 versions)6.1.176-1
Debian:13(1)
PackageVulnerable rangeFixed inDependents
linux6.12.38-1 ... 6.12.86-1~bpo12+1 (19 versions)6.12.86-1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
linux6.12.100-1 ... 7.0.4-1~bpo13+1 (131 versions)7.0.4-1

Weakness Classification(1)

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

Additional Vendor Advisories

(20)

Data Freshness Timeline

(refreshed 5× in last 7d / 86× 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 240 total refreshes for this CVE.

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

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 0% probability of exploitation in the next 30 days, which ranks it in the top 97.1% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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.