CVE-2026-46075: crypto: atmel-sha204a - Fix potential UAF and memory leak in remove path
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.
Security readout for executives and security teams
Plain-English summary
CVE-2026-46075 is a Linux kernel driver cleanup bug. Systems using the Atmel SHA204A hardware random-number driver could hit unsafe memory use or a leak when the device is removed. The available sources do not provide CVSS severity, public exploitation, or broad impact claims.
Executive priority
Treat as targeted kernel maintenance unless your fleet uses embedded or hardware-security platforms with Atmel SHA204A support. Prioritize confirmation and patch tracking, not emergency response, because severity and exploitation evidence are currently incomplete.
Technical view
The atmel-sha204a crypto driver remove path failed to fully prevent new hwrng read callbacks and queued I2C work before teardown. A queued callback during device removal could cause use-after-free. An early return could also leave sysfs entries and hwrng private data allocated.
Likely exposure
Exposure appears limited to Linux systems with the atmel-sha204a driver and relevant Atmel SHA204A I2C hardware or configuration. Generic Linux servers without this driver or hardware are less likely to be affected, but kernel build and module inventory should confirm.
Exploitation context
The source bundle marks KEV as false and cites no active exploitation. The described condition occurs during driver/device removal, involving hwrng reads and queued work during teardown. Evidence is insufficient to claim remote exploitation, privilege impact, or exploitation in the wild.
Researcher notes
Focus review on the atmel-sha204a remove path, hwrng unregister ordering, queued I2C work flushing, sysfs cleanup, and hwrng private data lifetime. The public record lacks CVSS, CWE, and exploitability analysis, so avoid over-scoring without local exposure evidence.
Mitigation direction
Apply vendor kernel updates that include the referenced stable atmel-sha204a fixes.
Track distribution advisories for affected kernel packages and backports.
Prioritize systems where atmel-sha204a is built, loaded, or attached to hardware.
If unused, assess disabling the driver through approved kernel configuration guidance.
Validation and detection
Inventory kernel versions and compare against vendor advisories or referenced stable commits.
Check whether the atmel-sha204a module is built or loaded on target systems.
Identify systems with Atmel SHA204A I2C hardware or board configurations.
Confirm patched kernels unregister hwrng and flush I2C work before teardown.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cve · low confidence lookup
CVE-2026-46075 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
0CVSS vectors
3Timeline events
0ADP providers
7Source links
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
CVE publishedCVE Program
The CVE record was published.
May 27, 2026, 12:58 UTC (UTC+00:00)
CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.