VYPR
Unrated severityNVD Advisory· Published Dec 16, 2025· Updated Apr 15, 2026

CVE-2025-68313

CVE-2025-68313

Description

In the Linux kernel, the following vulnerability has been resolved:

x86/CPU/AMD: Add RDSEED fix for Zen5

There's an issue with RDSEED's 16-bit and 32-bit register output variants on Zen5 which return a random value of 0 "at a rate inconsistent with randomness while incorrectly signaling success (CF=1)". Search the web for AMD-SB-7055 for more detail.

Add a fix glue which checks microcode revisions.

[ bp: Add microcode revisions checking, rewrite. ]

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

AMD Zen5 CPUs have a bug where RDSEED 16/32-bit outputs can produce zero while falsely indicating success, requiring microcode updates.

Root

Cause

A hardware defect in AMD Zen5 processors causes the RDSEED instruction's 16-bit and 32-bit register output variants to return a random value of zero at a rate inconsistent with randomness. Critically, the processor incorrectly signals success by setting the carry flag (CF=1), misleading software into trusting the returned value. This issue is documented in AMD-SB-7055 [1].

Exploitation

The vulnerability is inherent to the CPU hardware and can be triggered by any software that uses RDSEED to obtain random numbers. No authentication or special privileges are required; any user process executing RDSEED on an affected Zen5 core may receive a zero value while the CPU reports success. The attack surface includes cryptographic applications, secure key generation, and any system relying on hardware random number generation for security.

Impact

An attacker who can observe or influence the output of RDSEED on an affected system may force the use of a known zero value instead of unpredictable randomness. This could weaken cryptographic operations, compromise key material, or undermine security protocols that depend on high-quality entropy. The bug degrades the trustworthiness of the hardware random number generator.

Mitigation

The fix involves a microcode update that adds revision checking to ensure the RDSEED instruction behaves correctly. The patch has been applied to the stable Linux kernel tree [1]. Users should update their systems with the latest microcode and kernel patches to resolve the issue. No workaround is available without a microcode update.

AI Insight generated on May 19, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.

Affected products

2

Patches

0

No patches discovered yet.

Vulnerability mechanics

AI mechanics synthesis has not run for this CVE yet.

References

3

News mentions

0

No linked articles in our index yet.