Answer in brief
CVE-2026-74402 records a Unknown severity vulnerability in crypto: atmel-sha204a - fix blocking and non-blocking rng logic. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-74402 records a Unknown severity vulnerability in crypto: atmel-sha204a - fix blocking and non-blocking rng logic. The current sources do not mark it as known exploited. The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <76269a91fd9560c5f03c3e59421a0329e39a6661 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <9039bb4f238474379221fc933c34f19f0cba501b || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <d4aa6141ff03ec82eed6fcef814300fb855ce5d8 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <e833e865e4944ba75120db534bd931db6cf677d3 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <2fa302bbc62dec7cb6339c9494e0e3f2f884afeb || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <aac63bbea8fd5a34f1a4305cb73369068f952d32 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <938ae1fb4a8f5db43b62b6206d409efbf317f0d9 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <319400fc5ee15db5793aa45f854968141326effc | 76269a91fd9560c5f03c3e59421a0329e39a6661, 9039bb4f238474379221fc933c34f19f0cba501b, d4aa6141ff03ec82eed6fcef814300fb855ce5d8, e833e865e4944ba75120db534bd931db6cf677d3, 2fa302bbc62dec7cb6339c9494e0e3f2f884afeb, aac63bbea8fd5a34f1a4305cb73369068f952d32, 938ae1fb4a8f5db43b62b6206d409efbf317f0d9, 319400fc5ee15db5793aa45f854968141326effc |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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
Quoted source text, attributed separately from HOL analysis.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Linux/Linux (generic), Linux/Linux (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Linux/Linuxgeneric | >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <76269a91fd9560c5f03c3e59421a0329e39a6661 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <9039bb4f238474379221fc933c34f19f0cba501b || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <d4aa6141ff03ec82eed6fcef814300fb855ce5d8 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <e833e865e4944ba75120db534bd931db6cf677d3 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <2fa302bbc62dec7cb6339c9494e0e3f2f884afeb || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <aac63bbea8fd5a34f1a4305cb73369068f952d32 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <938ae1fb4a8f5db43b62b6206d409efbf317f0d9 || >=da001fb651b00e1deeaf24767dd691ae8152a4f5 <319400fc5ee15db5793aa45f854968141326effc | 76269a91fd9560c5f03c3e59421a0329e39a6661, 9039bb4f238474379221fc933c34f19f0cba501b, d4aa6141ff03ec82eed6fcef814300fb855ce5d8, e833e865e4944ba75120db534bd931db6cf677d3, 2fa302bbc62dec7cb6339c9494e0e3f2f884afeb, aac63bbea8fd5a34f1a4305cb73369068f952d32, 938ae1fb4a8f5db43b62b6206d409efbf317f0d9, 319400fc5ee15db5793aa45f854968141326effc |
| Linux/Linuxgeneric | 5.3 | Not reported |
Published upstream
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 15, 2026
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
Quoted source text, attributed separately from HOL analysis.