CVE-2026-74402

crypto: atmel-sha204a - fix blocking and non-blocking rng logic

N/A
Published: August 15, 2026 at 05:59 AM UTC
Updated: August 17, 2026 at 06:19 AM UTC
1 product affected across 1 vendorLinux Kernel

Using Linux by Linux?

Get instant alerts when new vulnerabilities affect Linux - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
N/A
Exploit prediction
EPSS 0.2%

Description

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

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

5.3 ≤ v < 5.10.2615.3 ≤ v < 5.15.2125.3 ≤ v < 6.1.1785.3 ≤ v < 6.12.975.3 ≤ v < 6.18.405.3 ≤ v < 6.6.1455.3 ≤ v < 7.1.55.3 ≤ v < 7.25.3da001fb651b00e1deeaf24767dd691ae8152a4f5
Vendor states this is fixed in 2fa302bbc62dec7cb6339c9494e0e3f2f884afeb (fixed)
Vendor states this is fixed in 319400fc5ee15db5793aa45f854968141326effc (fixed)
Vendor states this is fixed in 76269a91fd9560c5f03c3e59421a0329e39a6661 (fixed)
Vendor states this is fixed in 9039bb4f238474379221fc933c34f19f0cba501b (fixed)
Vendor states this is fixed in 938ae1fb4a8f5db43b62b6206d409efbf317f0d9 (fixed)
Vendor states this is fixed in aac63bbea8fd5a34f1a4305cb73369068f952d32 (fixed)
Vendor states this is fixed in d4aa6141ff03ec82eed6fcef814300fb855ce5d8 (fixed)
Vendor states this is fixed in e833e865e4944ba75120db534bd931db6cf677d3 (fixed)
Vendor states this is fixed in 5.10.261 (unaffected)
Vendor states this is fixed in 5.15.212 (unaffected)
Vendor states this is fixed in 5.3 (unaffected)
Vendor states this is fixed in 6.1.178 (unaffected)
Vendor states this is fixed in 6.12.97 (unaffected)
Vendor states this is fixed in 6.18.40 (unaffected)
Vendor states this is fixed in 6.6.145 (unaffected)
Vendor states this is fixed in 7.1.5 (unaffected)
Vendor states this is fixed in 7.2 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet, and no fixed version or vendor advisory is recorded against it.

Quick Info

StatusRECEIVED

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card