CVE-2026-74402 — crypto: atmel-sha204a - fix blocking and non-blocking rng logic
In the Linux kernel, the following vulnerability has been resolved: crypto: atmel-sha204a - fix blocking and non-blocking rng logic The blocking and non-blocking paths were failing to provide valid entropy due to improper buffer management. Reading the buffer starting from byte 1, only fetch the 32 bytes of random data from the return message. Tested on an Atmel SHA204A device. Before (here for blocking), tests showed repeatedly reading reduced bytes. $ head -c 32 /dev/hwrng | hexdump -C 00000000 02 28 85 b3 47 40 f2 ee 00 00 00 00 00 00 00 00 |.(..G@..........| 00000010 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................| 00000020 After, the result will be similar to the following: $ head -c 32 /dev/hwrng | hexdump -C 00000000 5a fc 3f 13 14 68 fe 06 68 0a bd 04 83 6e 09 69 |Z.?..h..h....n.i| 00000010 75 ff cf 87 10 84 3b c9 c1 df ae eb 45 53 4c c3 |u.....;.....ESL.| 00000020
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.2% (30-day exploitation probability)+2
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Linux Linux).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Linux | Linux |
≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 76269a91fd9560c5f03c3e59421a0329e39a6661≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 9039bb4f238474379221fc933c34f19f0cba501b≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < d4aa6141ff03ec82eed6fcef814300fb855ce5d8≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < e833e865e4944ba75120db534bd931db6cf677d3≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 2fa302bbc62dec7cb6339c9494e0e3f2f884afeb≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < aac63bbea8fd5a34f1a4305cb73369068f952d32≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 938ae1fb4a8f5db43b62b6206d409efbf317f0d9≥ da001fb651b00e1deeaf24767dd691ae8152a4f5 and < 319400fc5ee15db5793aa45f854968141326effc and 1 moreversion 5.3 |
Vulnerable | CVE Program (cve.org) e CISA ADP |
EPSS over time FIRST
Oct 15, 2026 → Oct 29, 2026 · 14 reading(s) · max 0.22%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Not enough vector or weakness data: use the affected application’s logs as a starting point.
Timeline
What happened to this CVE, newest first.
- 2026
- Record published
- Affected products added · linux/linux
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
8 on the record
- git.kernel.org/stable/c/2fa302bbc62dec7cb6339c9494e0e3f2f884afeb
- git.kernel.org/stable/c/d4aa6141ff03ec82eed6fcef814300fb855ce5d8
- git.kernel.org/stable/c/938ae1fb4a8f5db43b62b6206d409efbf317f0d9
- git.kernel.org/stable/c/9039bb4f238474379221fc933c34f19f0cba501b
- git.kernel.org/stable/c/76269a91fd9560c5f03c3e59421a0329e39a6661
- git.kernel.org/stable/c/aac63bbea8fd5a34f1a4305cb73369068f952d32
- git.kernel.org/stable/c/e833e865e4944ba75120db534bd931db6cf677d3
- git.kernel.org/stable/c/319400fc5ee15db5793aa45f854968141326effc
Elsewhere on this site
Related CVEs (same products)
- Unknown CVE-2026-99216 Drivers: hv: Don't reset VMBus connection state on error/exit paths 2d
- Unknown CVE-2026-99215 power: supply: core: prevent unregistering a power supply while a callback runs 2d
- Unknown CVE-2026-99207 scsi: target: Disable interrupts while holding delayed_cmd_lock 2d
- Unknown CVE-2026-99208 drm/xe/oa: Zero OA buffer at allocation 2d
- Unknown CVE-2026-99209 drm/xe: skip eviction of a BO with no resource 2d
- Unknown CVE-2026-99210 accel/rocket: clear rdev on device init failure 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CVSS score published by NVD, the CNA, CISA or GitHub so far.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-74402 is "crypto: atmel-sha204a - fix blocking and non-blocking rng logic", rated Unknown. It affects Linux (Linux); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. EPSS 0.22% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.