CVE-2025-0577 | Glibc: vdso getrandom acceleration may return predictable randomness

An insufficient entropy vulnerability was found in glibc. The getrandom and arc4random family of functions may return predictable randomness if these functions are called again after the fork, which happens concurrently with a call to any of these functions.

Published: 2026-02-18 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2025-0577 is rated Low Risk (20.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.02%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-0577

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-21 0.08% 0.02% -0.06%
2 2026-02-28 0.02% 0.08% +0.06%
3 2026-02-19 0.02%

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-0577

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.8 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.2 2.5 [email protected]

Weakness enumeration for CVE-2025-0577

OS Trackers for CVE-2025-0577

vendor priority summary link
debian unimportant CVE-2025-0577 unimportant priority: Debian including 1 source packages (glibc), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-0577
redhat medium https://access.redhat.com/security/cve/CVE-2025-0577
suse medium CVE-2025-0577 severity moderate: SUSE including 19 source package names (glibc, glibc-32bit, …), 293 product×package rows across 35 product lines (SLES-LTSS-TERADATA 15 SP2, SUSE Linux Enterprise High Performance Computing 15 SP3-LTSS, … (35 product lines)): Known Not Affected 293. https://www.suse.com/security/cve/CVE-2025-0577/
ubuntu medium CVE-2025-0577 medium priority: Ubuntu including 2 source packages (eglibc, glibc), 13 status rows across 8 suites (bionic, focal, jammy, noble, oracular, trusty, upstream, xenial): not-affected 9, DNE 4. https://ubuntu.com/security/CVE-2025-0577

Affected software / configurations for CVE-2025-0577

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-0577

cvelogic Threat Intelligence