In the Linux kernel, the following vulnerability has been resolved:
crypto: drbg - Fix returning success on failure in CTR_DRBG
drbg_ctr_generate() sometimes returns success when it fails, leaving the output buffer uninitialized. Fix it.
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
In the Linux kernel, the following vulnerability has been resolved:
crypto: drbg - Fix returning success on failure in CTR_DRBG
drbg_ctr_generate() sometimes returns success when it fails, leaving the output buffer uninitialized. Fix it.
July 25, 2026
August 17, 2026
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | 5.10.103-1 ... 5.10.92-2 (55 versions) | 5.10.262-1 | — |
| linux-6.1 | 6.1.106-3~deb11u1 ... 6.1.177-1~deb11u1 (22 versions) | 6.1.180-1~deb11u1 | — |
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | 6.1.106-1 ... 6.1.99-1 (55 versions) | 6.1.180-1 | — |
| linux-6.12 | — | 6.12.100-1~deb12u1 | — |
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | 6.12.38-1 ... 6.12.95-1~bpo12+1 (30 versions) | 6.12.96-1 | — |
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| linux | 6.12.100-1 ... 7.1~rc7-1~exp1 (156 versions) | 7.1.4-1 | — |
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-64306
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.