Kernel memory corruption via teardown race
Published May 27, 2026 · Updated May 27, 2026
Use-after-free in the Linux Kernel Atmel SHA204A driver allows local users to corrupt kernel memory during device removal. The remove path leaves the hardware random-number generator registered and does not flush its I2C workqueue, so a queued read callback can access freed device state; an early return also leaks sysfs state and hwrng.priv. Reachability requires an Atmel SHA204A device, local low-privileged access, and concurrent device removal; no resulting privilege escalation or code execution has been publicly demonstrated.
Summary
What happened
Use-after-free in the Linux Kernel Atmel SHA204A driver allows local users to corrupt kernel memory during device removal. The remove path leaves the hardware random-number generator registered and does not flush its I2C workqueue, so a queued read callback can access freed device state; an early return also leaks sysfs state and hwrng.priv. Reachability requires an Atmel SHA204A device, local low-privileged access, and concurrent device removal; no resulting privilege escalation or code execution has been publicly demonstrated.
The record
- CVE
- CVE-2026-46075
- Published
- May 27, 2026
- Updated
- May 27, 2026
- Vendor
- The Linux Kernel Organization
- Product
- Linux Kernel
- Classifications
- CWE-416, T1499.004
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 27, 2026CVE publishedPublication date reported by the CVE source.
- May 27, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=5.3
- Affected versionversion=da001fb651b00e1deeaf24767dd691ae8152a4f5 <1193c12126d39bf986a5a9214827b73707b193ab
- Affected versionversion=da001fb651b00e1deeaf24767dd691ae8152a4f5 <31901371ccd16b42d2f167b1018ba9ae8bd5a6c7
- Affected versionversion=da001fb651b00e1deeaf24767dd691ae8152a4f5 <775c00d87c385b758da9504cf053acea00e2ed40
- Affected versionversion=da001fb651b00e1deeaf24767dd691ae8152a4f5 <bab1adf3b87e4bfac92c4f5963c63db434d561c1
- Affected versionversion=da001fb651b00e1deeaf24767dd691ae8152a4f5 <c5a45d14234bf26e28a89e3a5dcc08336595cf11
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo