CVE-2025-2509

Exp

Out-of-Bounds Read in Virglrenderer in ChromeOS 16093.57.0 allows a malicious guest VM to achieve arbitrary address access within the crosvm sandboxed process, potentially leading to VM escape via crafted vertex elements data triggering an out-of-bounds read in util_format_description.

Published: 2025-05-06 Last update: 2025-10-03 Assigner: 7f6e188d-c52a-4a19-8674-3c3fa7d1fc7f Source: 7f6e188d-c52a-4a19-8674-3c3fa7d1fc7f

Conclusion & alert: CVE-2025-2509 is rated Exploit Available (50/100): CVSS High severity, with low exploitation likelihood (EPSS 0.01%). Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB). Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

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

Public exploit references (Exploit-DB) for CVE-2025-2509

EDB-ID Source Kind Published Link
nvd_ref exploit_tag Exploit-DB ↗

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

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 2025-05-06 0.01%

Full EPSS history (1 record total)

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

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
7.8 3.1 HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2025-2509

OS Trackers for CVE-2025-2509

vendor priority summary link
debian unimportant CVE-2025-2509 unimportant priority: Debian including 1 source packages (virglrenderer), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-2509
ubuntu medium CVE-2025-2509 medium priority: Ubuntu including 1 source packages (virglrenderer), 7 status rows across 7 suites (bionic, focal, jammy, noble, oracular, plucky, upstream): not-affected 6, released 1. https://ubuntu.com/security/CVE-2025-2509

Affected software / configurations for CVE-2025-2509

Vendor Product Version Raw CPE
google chrome_os 16093.57.0 cpe:2.3:o:google:chrome_os:16093.57.0:*:*:*:*:*:*:*

References for CVE-2025-2509

cvelogic Threat Intelligence