In Libgcrypt 1.8.4, the C implementation of AES is vulnerable to a flush-and-reload side-channel attack because physical addresses are available to other processes. (The C implementation is used on platforms where an assembly-language implementation is unavailable.) NOTE: the vendor's position is that the issue report cannot be validated because there is no description of an attack
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Alpine Linux | — | Upgrade libgcrypt | Nov 8, 2019 | Jun 19, 2019 |
| Huawei Euleros 2_0_sp8 | — | Upgrade libgcrypt-develUpgrade libgcrypt | Nov 19, 2019 | Jun 20, 2019 |
| Redhat_linux | — | No solution exists | Jul 9, 2025 | Jun 20, 2019 |
| Suse | — | Upgrade libgcrypt-devel-32bitUpgrade libgcrypt-cavsUpgrade libgcrypt20-32bitUpgrade libgcrypt20Upgrade libgcrypt-develUpgrade libgcrypt20-hmacUpgrade libgcrypt20-hmac-32bit | Jul 24, 2019 | Jun 20, 2019 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Jan 20, 2025 | Jun 19, 2019 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub